It is just a hunch based on the root cause of that issue, a removed destination reference remaining in the connection contex.
Feel free to open a separate issue, to be convinced we need a test case. On 4 July 2011 11:02, James Green <james.mk.gr...@gmail.com> wrote: > How convinced are you? > > I'm minded to file this as a seperate bug given the heap exceptions being > thrown and the Stomp connectivity that dies completely. What is not > explained in the bug report you list are the "other effects" of the bug > Timothy has fixed and whether there may be any overlap in the behaviours > being observed. > > James > > On 4 July 2011 10:44, Gary Tully <gary.tu...@gmail.com> wrote: > >> this looks like a bug, but I think it may be an instance of >> https://issues.apache.org/jira/browse/AMQ-2524 which has just been >> resolved so it is available in the most current 5.6-SNAPSHOT >> >> On 4 July 2011 09:31, James Green <james.mk.gr...@gmail.com> wrote: >> > Getting these: >> > >> > 2011-07-03 07:41:54,330 | INFO | Transport failed: java.io.EOFException >> | >> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ >> > Transport: tcp:///127.0.0.1:53546 >> > 2011-07-03 07:49:05,893 | INFO | Transport failed: java.io.EOFException >> | >> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ >> > Transport: tcp:///127.0.0.1:42055 >> > 2011-07-03 07:49:05,894 | INFO | Transport failed: java.io.EOFException >> | >> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ >> > Transport: tcp:///127.0.0.1:42045 >> > 2011-07-03 08:06:55,985 | INFO | Transport failed: java.io.EOFException >> | >> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ >> > Transport: tcp:///127.0.0.1:43304 >> > 2011-07-03 08:06:55,987 | INFO | Outbound.Account.22556 Inactive for >> longer >> > than 60000 ms - removing ... | org.apache.activemq.broker.region.Queue | >> > ActiveMQ Broker[zorin] Scheduler >> > 2011-07-03 08:06:59,566 | WARN | Async error occurred: >> > java.lang.OutOfMemoryError: Java heap space | >> > org.apache.activemq.broker.TransportConnection.Service | ActiveMQ >> Transport: >> > tcp:///127.0.0.1:42987 >> > 2011-07-03 08:06:59,566 | INFO | Outbound.Account.21011 Inactive for >> longer >> > than 60000 ms - removing ... | org.apache.activemq.broker.region.Queue | >> > ActiveMQ Broker[zorin] Scheduler >> > 2011-07-03 08:06:59,567 | WARN | Exception occurred processing: >> > null: java.lang.OutOfMemoryError: Java heap space | >> > org.apache.activemq.transport.stomp.ProtocolConverter | ActiveMQ >> Connection >> > Dispatcher: /127.0.0.1:42987 >> > >> > 2011-07-03 09:00:51,867 | INFO | Transport failed: java.io.EOFException >> | >> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ >> > Transport: tcp:///127.0.0.1:57612 >> > 2011-07-03 09:00:51,868 | INFO | Transport failed: java.io.EOFException >> | >> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ >> > Transport: tcp:///127.0.0.1:57634 >> > 2011-07-03 09:00:51,868 | INFO | Transport failed: java.io.EOFException >> | >> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ >> > Transport: tcp:///127.0.0.1:57610 >> > 2011-07-03 09:00:54,148 | INFO | Transport failed: java.io.EOFException >> | >> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ >> > Transport: tcp:///127.0.0.1:57643 >> > 2011-07-03 09:00:56,406 | INFO | Transport failed: java.io.EOFException >> | >> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ >> > Transport: tcp:///127.0.0.1:57644 >> > 2011-07-03 09:00:57,535 | INFO | Transport failed: java.io.EOFException >> | >> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ >> > Transport: tcp:///127.0.0.1:57646 >> > 2011-07-03 09:00:57,536 | INFO | Transport failed: java.io.EOFException >> | >> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ >> > Transport: tcp:///127.0.0.1:57659 >> > 2011-07-03 09:00:57,536 | INFO | Transport failed: java.io.EOFException >> | >> > org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ >> > Transport: tcp:///127.0.0.1:57676 >> > 2011-07-03 13:32:36,995 | INFO | Outbound.Account.200237 Inactive for >> > longer than 60000 ms - removing ... | >> > org.apache.activemq.broker.region.Queue | ActiveMQ Broker[zorin] >> Scheduler >> > 2011-07-03 23:58:46,994 | INFO | account_events Inactive for longer than >> > 60000 ms - removing ... | org.apache.activemq.broker.region.Queue | >> ActiveMQ >> > Broker[zorin] Scheduler >> > >> > The web console responds fine, the Stomp connector throws the exception. >> The >> > AMQ config shows -Xms512M -Xmx512M >> > -Dorg.apache.activemq.UseDedicatedTaskRunner=true >> > >> > This system has been running without incident for several months. Two >> weeks >> > ago I changed the config to enable gcInactiveDestinations="true" on >> queues. >> > Since then we've had two Stomp "crashes" inside one week. >> > >> > Does this GC process require much more RAM or something? Or am I likely >> > looking at a bug? >> > >> > Thanks, >> > >> > James >> > >> >> >> >> -- >> http://fusesource.com >> http://blog.garytully.com >> > -- http://fusesource.com http://blog.garytully.com
