I experience losing messages when they are received with the same xid when messages are received in parallel. This means case that prior message is not yet fully processed when meanwhile new message is promoted for being processed.
This is the scenario which behaves wrong by my view
- EIS passes a message with xid1 to RAR to be processed
- first message is passed as work to be process (stays in progress)
- EIS passes a second message with xid1 to RAR to be processed
- the second message is forgotten. It will never reach a MessageListner
- no error is returned or shown in log
Compared following scenario passes without a problem.
- EIS passes a message with xid1 to RAR to be processed
- first message is fully processed with MessageListner (it reaches the end of the onMessage method)
- EIS passes a second message with xid1 to RAR to be processed
- second message is processed by MessageListener
From logging I can see that work was cancelled by call of WorkWrapper [1]. But any information is forgotten. There is no error message in the log and there is wrong type and listnener methods called (javax.resource.spi.work.WorkListener by workCompleted with work type defined with status 4) for such messages.
- clones
-
JBEAP-5732 No error message on concurrent processing of the same inflow transaction
- Verified
- is caused by
-
JBJCA-1329 No error message on concurrent processing of the same inflow transaction
- Resolved
- is incorporated by
-
JBEAP-6489 (7.0.z) Upgrade to IronJacamar from 1.3.4 to 1.3.5
- Closed