[
https://issues.jboss.org/browse/WFLY-8243?page=com.atlassian.jira.plugin....
]
Flavia Rainone moved JBEAP-9130 to WFLY-8243:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8243 (was: JBEAP-9130)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
EJB
JMS
(was: Clustering)
(was: EJB)
(was: JMS)
Affects Version/s: (was: 7.1.0.DR8)
(was: 7.1.0.DR10)
(was: 7.1.0.DR11)
(was: 7.1.0.DR12)
Affects Testing: (was: Regression)
Clustered Singleton MDB does not activate
-----------------------------------------
Key: WFLY-8243
URL:
https://issues.jboss.org/browse/WFLY-8243
Project: WildFly
Issue Type: Bug
Components: Clustering, EJB, JMS
Reporter: Flavia Rainone
Assignee: Flavia Rainone
Priority: Blocker
Clustered Singleton MDB does not activate. It's regression in EAP 7.1.0.DR8 (against
DR7).
Customer impact: No Clustered Singleton MDB will activate in cluster and service will not
operate. No warning or error will show in server logs. There is no workaround for this
issue.
Test scenario:
- Start two EAP 7.1.0.DR8 servers in cluster with active delivery-group named
"group"
- Deploy queues InQueue and OutQueue to both of the servers. There is also Artemis
cluster configured between servers so all messages will be load-balanced between the
nodes.
- Deploy MDB configured as clustered singletons to both of the server. MDBs belong to
delivery-group "group"
-- MDB consumes messages from InQueue and resends to OutQueue
- Start sending messages to InQueue and consume from OutQueue.
- Check that MDB on node 1 is active as it's sigleton master
- Check that MDB on node 2 is NOT active
- Kill node-1 (by kill -9 ...)
- Check that MDB on node 2 is active as it's sigleton master
Expected result:
Consumer will receive all messages from OutQueue. All checks passes.
Actual result:
MDB on node 1 is not delivery active at the beginning of the test. Consumer timed out as
there are no processed messages in OutQueue
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)