You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Lasindu Charith (JIRA)" <ji...@apache.org> on 2015/06/12 18:39:00 UTC
[jira] [Commented] (STRATOS-1430) Stratos 4.1: Application fails
to un-deploy completely under certain circumstances
[ https://issues.apache.org/jira/browse/STRATOS-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583663#comment-14583663 ]
Lasindu Charith commented on STRATOS-1430:
------------------------------------------
Fixed in commit 03de83172309c2932075fb5284c120ca610bbf0a
> Stratos 4.1: Application fails to un-deploy completely under certain circumstances
> -----------------------------------------------------------------------------------
>
> Key: STRATOS-1430
> URL: https://issues.apache.org/jira/browse/STRATOS-1430
> Project: Stratos
> Issue Type: Bug
> Components: Autoscaler
> Affects Versions: 4.1.0 RC2
> Reporter: Martin Eppel
> Attachments: wso2carbon.zip
>
>
> • After the “Application undeployment process started” is started, there is a likelihood that (a few) VMs are still launched – I suspect this is due to some race condition between “Application undeployment process started” and the “autoscaler”.
> • All Vms which were launched before the “Application undeployment process started” get terminated as part of the undeployment process.
> • Vms which were launched after “Application undeployment process started” eventually get moved to obsolete / pending state and cleaned up, this can take up to 15- 20 minutes.
> • The application never gets completely removed,
> • The following exception is consistently observed:
> ID: [0] [STRATOS] [2015-06-05 20:47:07,237] WARN {org.apache.stratos.common.concurrent.locks.ReadWriteLock} - System warning! Trying to release a lock which has not been taken by the same thread: [lock-name] application-holder [thread-id] 114 [thread-name] pool-24-thread-2
> TID: [0] [STRATOS] [2015-06-05 20:47:07,237] ERROR {org.apache.stratos.messaging.message.receiver.topology.TopologyEventMessageDelegator} - Failed to retrieve topology event message
> org.apache.stratos.common.exception.InvalidLockRequestedException: System error, cannot acquire a write lock while having a read lock on the same thread: [lock-name] application-holder [thread-id] 114 [thread-name] pool-24-thread-2
> at org.apache.stratos.common.concurrent.locks.ReadWriteLock.acquireWriteLock(ReadWriteLock.java:114)
> at org.apache.stratos.autoscaler.applications.ApplicationHolder.acquireWriteLock(ApplicationHolder.java:60)
> •
> see also email thread (on dev list): Testing Stratos 4.1: Application undeployment: application fails to undeploy (nested grouping, group scaling)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)