No error message on concurrent processing of the same inflow transaction ------------------------------------------------------------------------ Key: JBJCA-1329 URL: https://issues.jboss.org/browse/JBJCA-1329 Project: IronJacamar Issue Type: Bug Components: Core Affects Versions: WildFly/IronJacamar 1.3.4.Final Reporter: Ondra Chaloupka Assignee: Jesper Pedersen 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}} By reading jca spec and description of JBTM-2164 I do understand that several messages could be passed with the same xid in parrarel. If my interpretation or scenario setup is wrong, please, let me know.