Is the AMQ broker embedded? If so, perhaps another application is leaking memory.
Or, are there any custom plugins? Bottom line here - there is something taking up all of the memory, causing the OOM condition. Taking heap dumps and/or histograms may be the only quick way to find out just what's consuming that memory. The heap charts in jconsole and visualvm can give an indication of whether this is a gradual problem over time (such as a slow memory leak), or a sudden event (such as an application with an oversize transaction flooding the broker). -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-hangs-and-i-don-t-understand-why-tp4709963p4709980.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
