I have a server that embeds an ActiveMQ broker and exports a Lingo Remotable service. The server often gets into a bad state where tons of exceptions like the ones below are logged to console and CPU is pegged by this endless loop of exceptions. This seems to happen after the server runs for several hours. Any idea what might be closing the "consumer"? The client to this app is up when the server gets into this state and the conversations between the client and server are short request-reposonse's.
2007-04-09 09:38:51,265 ERROR [ org.springframework.jms.listener.DefaultMessageListenerContainer] - <Execution of JMS message listener failed> javax.jms.IllegalStateException: The Consumer is closed at org.apache.activemq.ActiveMQMessageConsumer.checkClosed( ActiveMQMessageConsumer.java:610) at org.apache.activemq.ActiveMQMessageConsumer.receive( ActiveMQMessageConsumer.java:466) at org.springframework.jms.listener.DefaultMessageListenerContainer.doExecuteListener (DefaultMessageListenerContainer.java:301) at org.springframework.jms.listener.DefaultMessageListenerContainer.executeListener (DefaultMessageListenerContainer.java:292) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run (DefaultMessageListenerContainer.java:367) at org.springframework.core.task.SimpleAsyncTaskExecutor$ConcurrencyThrottlingRunnable.run (SimpleAsyncTaskExecutor.java:203) at java.lang.Thread.run(Thread.java:534) Thanks, Sanjiv
