Below is the complete stack trace.
<ERROR><2008/01/10 10:43:23.127><21621663><> ExceptionListener receives a
JMS exception
<TRACE><2008/01/10 10:43:23.127><21621663><> Unregistering Message
Listener...
<TRACE><2008/01/10 10:43:23.127><21621663><> Notifying/signaling a waiting
thread...
<ERROR><2008/01/10 10:43:23.144><21621663><> ExceptionListener receives a
JMS exception
<TRACE><2008/01/10 10:43:23.144><21621663><> Unregistering Message
Listener...
<ERROR><2008/01/10 10:43:23.153><21621663><>
javax.jms.IllegalStateException: The Consumer is closed
at
org.apache.activemq.ActiveMQMessageConsumer.checkClosed(ActiveMQMessageConsumer.java:679)
at
org.apache.activemq.ActiveMQMessageConsumer.setMessageListener(ActiveMQMessageConsumer.java:352)
at
ss.integration.util.MessageConsumer.unregisterListener(MessageConsumer.java:205)
at
ss.integration.util.MessageConsumer.notifyWaitingThread(MessageConsumer.java:159)
at ss.integration.util.ExListener.onException(ExListener.java:26)
at
org.apache.activemq.ActiveMQConnection$3.run(ActiveMQConnection.java:1648)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
<TRACE><2008/01/10 10:43:23.153><21621663><> Notifying/signaling a waiting
thread...
<TRACE><2008/01/10 10:43:23.154><32019423><> Waiting thread awaken
<TRACE><2008/01/10 10:43:23.155><32019423><> closing subscriber...
<TRACE><2008/01/10 10:43:23.156><32019423><> subscriber closed
<TRACE><2008/01/10 10:43:23.156><32019423><> closing session...
<TRACE><2008/01/10 10:43:23.156><32019423><> session closed
<TRACE><2008/01/10 10:43:23.156><32019423><> closing topic connection...
<TRACE><2008/01/10 10:43:23.158><32019423><> Exception in close()
<TRACE><2008/01/10 10:43:23.158><32019423><> closing topic connection...
<TRACE><2008/01/10 10:43:23.159><32019423><> Exception in close()
<ERROR><2008/01/10 10:43:23.159><32019423><> Unable to connect to the JMS
Server
<ERROR><2008/01/10 10:43:23.159><32019423><> Error in MessageConsumer.start:
Unable to connect to the JMS Server
<TRACE><2008/01/10 10:43:23.160><32019423><> closing topic connection...
<TRACE><2008/01/10 10:43:23.160><32019423><> Exception in close()
<ERROR><2008/01/10 10:43:23.161><32019423><> Error in main: Unable to
connect to the JMS Server
<ERROR><2008/01/10 10:43:23.161><32019423><> StackTrace:
<ERROR><2008/01/10 10:43:23.163><32019423><>
Error Code: -1
ss.util.SystemException: Unable to connect to the JMS Server
at
ss.integration.util.MessageConsumer.startConnection(MessageConsumer.java:368)
at ss.integration.util.MessageConsumer.start(MessageConsumer.java:124)
at ss.integration.agent.sams.SInputStarter.start(SInputStarter.java:113)
at ss.integration.agent.sams.SInputStarter.main(SInputStarter.java:45)
activemqnewbie wrote:
>
> Subscriber closes with an exception(below)after consuming certain
> messages.This happens at different intervals.
> Appreciate if someone could let me know the reason and solution for this.
> Am using activemq 5.0,java 5.
> Is there any property/setting that i need to do ?
> Below is the stack trace.
> <ERROR><2008/01/10 10:43:23.127><21621663><> ExceptionListener receives a
> JMS exception <TRACE><2008/01/10 10:43:23.127><21621663><> Unregistering
> Message Listener... <TRACE><2008/01/10 10:43:23.127><21621663><>
> Notifying/signaling a waiting thread... <ERROR><2008/01/10
> 10:43:23.144><21621663><> ExceptionListener receives a JMS exception
> <TRACE><2008/01/10 10:43:23.144><21621663><> Unregistering Message
> Listener... <ERROR><2008/01/10 10:43:23.153><21621663><>
> javax.jms.IllegalStateException: The Consumer is closed at
> org.apache.activemq.ActiveMQMessageConsumer.checkClosed(ActiveMQMessageConsumer.java:679)
> at
> org.apache.activemq.ActiveMQMessageConsumer.setMessageListener(ActiveMQMessageConsumer.java:352)
>
>
>
> Thanks
>
>
--
View this message in context:
http://www.nabble.com/Consumer-is-closed-Exception-tp15022223s2354p15023961.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.