stratos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akila (JIRA)" <>
Subject [jira] [Commented] (STRATOS-1538) Application with more than one group in application level fails to undeploy
Date Wed, 02 Sep 2015 09:42:45 GMT


Akila commented on STRATOS-1538:

Fixed in 702bcf10248a1fd8cc9544fafc551a8100927367. Removed GroupStatusTerminatingProcessor
which caused ApplicationInstanceTerminatedEvent to be published mistakenly. This class is
not actually needed.

> Application with more than one group in application level fails to undeploy
> ---------------------------------------------------------------------------
>                 Key: STRATOS-1538
>                 URL:
>             Project: Stratos
>          Issue Type: Bug
>          Components: Autoscaler
>    Affects Versions: 4.1.1
>            Reporter: Pubudu Chinthaka Gunatilaka
>             Fix For: 4.1.2
> When there is more than one group in application level, it fails to undeploy. When one
group is terminated it will send the terminated event and application  will mark as terminated.
This will cause for removing other groups in the application level and it will keep the spawned
instances of that group. The following error message can be seen in the log due to this behaviour.
> java.lang.IllegalArgumentException: Could not terminate container, cluster context not
found: [cluster-id] wso2am-190-application.gateway-worker.wso2am-190-gw-worker.domain [member-id]
>         at
>         at
>         at
>         at
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at
> Fix would be not to send any terminated or terminating event at GroupStatusTerminatedProcessor
as there is no need of a such event for the listeners at this level. 

This message was sent by Atlassian JIRA

View raw message