3:31 a.m.
Wolf-Dieter Fink created AS7-5218:
-------------------------------------
Summary: 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
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.
--
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
3:33 a.m.
[
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
3:42 a.m.
[
https://issues.jboss.org/browse/AS7-5218?page=com.atlassian.jira.plugin.s...
]
Wolf-Dieter Fink updated AS7-5218:
----------------------------------
Steps to Reproduce:
- Start two nodes with standalone-ha.xml
- Deploy quickstart cluster-ha-singleton-ejb
- The timer is started once and log every ten seconds
- stop the node with the timer (Ctrl-Z in the console)
- wait for shunning and the timer start on the second
- resume the node (command fg)
- After the cluster is merged both timers are active
quickstart available here:
https://github.com/wfink/quickstart/blob/cluster-ha-singleton-ejb/cluster...
was:
- Start two nodes with standalone-ha.xml
- Deploy quickstart cluster-ha-singleton-ejb
- The timer is started once and log every ten seconds
- stop the node with the timer (Ctrl-Z in the console)
- wait for shunning and the timer start on the second
- resume the node (command fg)
- After the cluster is merged both timers are active
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
7:11 a.m.
[
https://issues.jboss.org/browse/AS7-5218?page=com.atlassian.jira.plugin.s...
]
Paul Ferraro updated AS7-5218:
------------------------------
Fix Version/s: 7.1.3.Final (EAP)
7.2.0.Alpha1
Git Pull Request: https://github.com/jbossas/jboss-as/pull/2743,
https://github.com/jbossas/jboss-as/pull/2744 (was:
https://github.com/jbossas/jboss-as/pull/2743,
https://github.com/jbossas/jboss-as/pull/2744)
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
Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
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
8:46 a.m.
[
https://issues.jboss.org/browse/AS7-5218?page=com.atlassian.jira.plugin.s...
]
SBS JIRA Integration updated AS7-5218:
--------------------------------------
Git Pull Request: https://github.com/jbossas/jboss-as/pull/2743,
https://github.com/jbossas/jboss-as/pull/2744 (was:
https://github.com/jbossas/jboss-as/pull/2743,
https://github.com/jbossas/jboss-as/pull/2744)
Forum Reference: https://community.jboss.org/message/755771#755771
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
Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
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
4521
days inactive
4558
days old
4 comments
3 participants
participants (3)
-
Paul Ferraro (JIRA) -
SBS JIRA Integration (JIRA)
-
Wolf-Dieter Fink (JIRA)