Gary, Thanks for the reply. It appears that the broker is throwing the exception when running the inactivity monitor. It seems to be able to handle message traffic fine but idleness seems to kill it (there's a moral here somewhere). We have seen the broker core dump after long periods of no activity but with clients still connected to it.
Perhaps we should be killing the connections on the client side after extended periods of idleness? -Jimmy Gary Tully wrote: > > Can you post your activemq.xml? It looks like you need to restrict the > memory usage of the broker and have it spool messages to disk when the > memory limits are reached. See some additional detail at > http://activemq.apache.org/javalangoutofmemory.html#java.lang.OutOfMemory-SpoolingMessagestoDisk > * > > * > 2009/10/12 tejeswara <tejesw...@gmail.com> > > > > -- > http://blog.garytully.com > > Open Source Integration > http://fusesource.com > > -- View this message in context: http://www.nabble.com/java-lang-OutOfMemoryError-tp25864372p25874223.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
