I can understand that, however, we're pretty much stuck with this version for different reasons. I was just hoping for someone to recognise problem and to chip in.
I guess it can also be valuable for other users stuck on 5.6.0, if there are any, to post my findings here. The thread- OOM causing ActiveMQ to get "stuck" seems like a bug that has been fixed in later versions, however, I don't think the root cause is located in ActiveMQ- code at all. An OOM- exception can be triggered by other reasons than a full heap it seems. I think we have some kind of "native" resource issues. -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
