Hello, I'm facing a situation where client go OutOfMemory due to ever growing transaction log in FailoverTransport.stateTracker.connectionStates[one specific connection].transactions.
The majority of recorded transactions contain three commands: 1. TransactionInfo BEGIN 2. The message the client sent as a response to a temp queue 3. TransactionInfo END I upgraded broker to 5.13.4, as the symptomps on the broker corresponded to https://issues.apache.org/jira/browse/AMQ-6194, but that only made the error on the broker go away. The client is an MDB with activemq-ra 5.13.3 running in Payara 4.1.161, listening on a queue. My question is what may be causing this behavior? Is it a bug? The transaction is surely commited as these responses on temp queues are delivered, so the broker must have received the commit command, it just looks it didn't get passed back to the connection. ----- --- Patrik Dudits -- View this message in context: http://activemq.2283324.n4.nabble.com/Messages-piling-up-in-FailoverTranport-tp4715072.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
