I'd recommend you run with a profiler and send us a link to the memory profile when you notice it getting close to getting an OutOfMemoryException.
Regards, Hiram On 5/24/07, Daryl Richter <[EMAIL PROTECTED]> wrote:
Hey- Last night one of our brokers, running a build of ActiveMQ 4.2-SNAPSHOT built a couple of weeks ago, crashed with the following output: WARN TcpTransport - Cannot set socket buffer size = 65536 Exception in thread "ActiveMQ Transport Server: ssl://localhost:62622" Exception in thread "ActiveMQ Connection Dispatcher: 24407889" Exception in thread "ActiveMQ Transport: tcp:///10.100.103.146:4280" Exception in thread " btpool0-0" java.lang.OutOfMemoryError: Java heap space Exception in thread "RMI RenewClean-[10.100.101.102:47825]" java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space ERROR TransportStatusDetector - failed to complete a sweep for blocked clients java.lang.OutOfMemoryError: Java heap space ERROR TransactionTemplate - Having to Rollback - caught an exception: java.io.IOException: Java excep tion: 'Java heap space: java.lang.OutOfMemoryError'. At this point the broker became unresponsive. Does that WARN have anything to do with it? There aren't timestamps so I can't tell the time sequence. We are connecting to this broker exclusively with Stomp clients. The throughput is not large, though there was active messaging at the time. Thanks! -- Daryl Richter -:- Fund Development Services 440 Park Avenue South -:- 14th Floor -:- Manhattan -:- NY -:- 10016 e://[EMAIL PROTECTED] o://212/920.3526 m://917/536.0789
-- Regards, Hiram Blog: http://hiramchirino.com
