Issue

We are deploying camel routes into an EAP 6.3 container and using the A-MQ 6.1 JCA connector to connect to a remote A-MQ instance.
Each camel route is consuming a message from a A-MQ queue wrapped in an XA transaction.

The JCA adapter has been configured to pool 20 connections, however in the hawtio console we’re seeing that the enqueue count on the ActiveMQ.Advisory.Connection topic keeps increasing. We also see CPU usage of the broker go up to 80% when their are 20 concurrent consumers deployed to EAP.

We used the camel project found here to test XA transactions:

https://github.com/noelo/EAPJMSXA

1. setup A-MQ 6.1

2. setup Postgres Database, and run create-psql.txt from the test case

3. setup EAP 6.3 standalone.xml from the test case

4. Compile and Deploy test case

5. Send messages to 'TESTQIN' on A-MQ

Observe the Enqueue Count going up on the ActiveMQ.Advisory.Connection topic in web console. Also if you increase the concurrentConsumers for jmsXA bean in camel-config.xml, you should see the high CPU for the Broker JVM.