-
Bug
-
Resolution: Done
-
Blocker
-
8.1.0.Beta
-
None
-
False
-
-
False
-
-
-
-
-
-
Known Issue
-
-
-
There is intermittent failure in test scenario with with EAP servers forming Artemis cluster and EAP servers with deployed MDBs connected through remote JCA to this cluster.
Customer impact: There may be lost messages in case of crash of EAP server in cluster with remote JCA connection.
Test scenario:
- There are 4 nodes. Node 1 and 3 are in Artemis cluster and started with queues InQueue and OutQueue on both of them.
- Start producer which sends 20000 messages (mix of small and large messages) to InQueue. Once producer finishes, deploy MDBs to nodes 2, 4 which read messages from InQueue and sends them to OutQueue (in XA transaction).
- Kill and start again node 1. Then kill and start node 3 on XA transaction commit (when org.apache.activemq.artemis.core.transaction.Transaction.commit() is called)
- Read all messages from OutQueue.
Expected result: Number of send and received messages is the same (20 000)
Actual result: Sometimes there are lost messages.
Investigation: I was tracking one of the lost messages (it's not large message) and see that it was processed on node-4 by MDB and sent to OutQueue to node-3 succesfully. From the traces it's visible that message was paged but it's not clear why it could not be read from OutQueue by receiver later on.
- is incorporated by
-
JBEAP-30130 (8.1.z) Upgrade Artemis from 2.33.0.redhat-00017 to 2.40.0.redhat-0005
-
- Verified
-