Scenario:
There are 4 EAP servers.
Servers 1, 3 are in cluster configured using Netty static connectors. They hold messages and they will be referenced in this text as JMS servers.
Servers 2, 4 are not in cluster. They have RA configured to connect to servers 1 and 3 server using Netty static connectors. They have MDBs which resend messages from InQueue to OutQueue. Servers 2, 4 will be referenced this text as MDB servers.
At the beginning of the test, standalone producer sends 10 000 messages to server 1.
MDBs are deployed to MDB servers.
JMS servers are restarted.
Test waits until all messages are resent from InQueue to OutQueue
Standalone receiver receives all messages from OutQueue on server 1.
Expectation: All messages sent to InQueue are received from OutQueue.
Reality: Sometimes happens that few messages are stuck on server 1 in InQueue.
Customer impact: It may happen that some messages are not properly delivered in time and restart of server is needed for rescheduling of delivery the messages.
This issue is not reported as blocker because the messages are not lost and this is intermittent issue occurring in edge case when events in cluster happens in specific order. This issue is present also in previous versions of EAP 7 - JBEAP-13228
- blocks
-
JBEAP-25103 EAP 8 - Undelivered messages after restart in cluster
- New
- is related to
-
JBEAP-13228 (7.2.z) Undelivered messages after restart in cluster
- Closed
- relates to
-
JBEAP-23608 (8.0.z) Messaging - Number of consumers should be almost equal on server restart
- New