[
https://issues.jboss.org/browse/AS7-5218?page=com.atlassian.jira.plugin.s...
]
Wolf-Dieter Fink updated AS7-5218:
----------------------------------
Description:
If a SingletonService is deployed on both nodes it will start on one node only, also it
works if nodes are leaving or joining the cluster if it is shutdowned, crashed or
started.
But in case of a cluster merge I expect that the method stop() will be called.
But the service is still running on two nodes after merge.
was:
If a SingletonService is deployed on both nodes it will start on one node only, also it
works if nodes are leaving or joining the cluster.
But in case of a cluster merge I expect that the method stop() will be called.
But the service is still running on two nodes after merge.
SingletonService is not stopped after cluster split/merge
---------------------------------------------------------
Key: AS7-5218
URL:
https://issues.jboss.org/browse/AS7-5218
Project: Application Server 7
Issue Type: Bug
Components: Clustering, MSC
Affects Versions: 7.1.2.Final (EAP)
Environment: Two servers in standalone-ha mode
Reporter: Wolf-Dieter Fink
Assignee: Paul Ferraro
Labels: cluster, service, singleton
If a SingletonService is deployed on both nodes it will start on one node only, also it
works if nodes are leaving or joining the cluster if it is shutdowned, crashed or
started.
But in case of a cluster merge I expect that the method stop() will be called.
But the service is still running on two nodes after merge.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira