Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final)
Affects Version/s: 7.1.2.Final (EAP)
Component/s: Clustering, MSC
Labels:

Steps to Reproduce:
Hide

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-ha-singleton-ejb
Show
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-ha-singleton-ejb
Forum Reference:
https://community.jboss.org/message/755771#755771
Git Pull Request:
https://github.com/jbossas/jboss-as/pull/2743, https://github.com/jbossas/jboss-as/pull/2744

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.

Attachments

Activity

People

Assignee:: Paul Ferraro

Reporter:: Wolf Fink

Votes:: 1 Vote for this issue

Watchers:: 7 Start watching this issue

Dates

Created:: 2012/07/19 4:29 AM

Updated:: 2022/09/09 6:12 AM

Resolved:: 2012/08/02 8:03 AM