Thank you, Martin, this is indeed a result of heap dump analysis. Under normal conditions the application operates happilly with around 800MB of heap as can be seen in visualvm. In these out of memory situations, 1.2 - 1.6 GBs is allocated in that very object in the description. It is always this connection that is used to put responses on temp queue. Other MDBs produce messages without FailoverTransport not cleaning commited transactions.
I'll surely try to find out a minimal example. I think this is only MDB that responds via transactional connection pool to a temp queue. Other put messages to normal queues, topics, or use non-transactional pool for sending to temp queues. ----- --- Patrik Dudits -- View this message in context: http://activemq.2283324.n4.nabble.com/Messages-piling-up-in-FailoverTranport-tp4715072p4715080.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
