activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From khandelwalanuj <khandelwal.anu...@gmail.com>
Subject After broker restart, subscirber is not able to connect
Date Mon, 22 Dec 2014 12:58:17 GMT
Hi,

Using ActiveMQ-5.10.

After restarting the broker, the client does not seem to be able to recover
and forever spits out. Clients throws

 [ 2014-12-18 18:17:58,852 [StatsCollector-3] 
jmx.TCAQueueSizeMonitor.getPendingQueueSize():68 ERROR]: Exception while
getting TCA queue size status!!!
 **javax.jms.IllegalStateException: The Session is closed**

        at
org.apache.activemq.ActiveMQSession.checkClosed(ActiveMQSession.java:767)
        at
org.apache.activemq.ActiveMQSession.createBrowser(ActiveMQSession.java:1425)
        at
org.apache.activemq.jms.pool.PooledSession.createBrowser(PooledSession.java:294)
        at
deshaw.moss.jmx.TCAQueueSizeMonitor.getPendingQueueSize(TCAQueueSizeMonitor.java:63)
        at
deshaw.moss.jmx.TCAQueueSizeMonitor.getTCAQueueSizeStatus(TCAQueueSizeMonitor.java:101)
        at
deshaw.moss.jmx.TCAHeartBeatStatsCollector.run(TCAHeartBeatStatsCollector.java:60)
        at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
        at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)


The Session is closed once and then after it below exception continuously
comes:

[ 2014-12-19 00:00:06,176 [securityEventDataSubscriberContainer-4105] 
listener.DefaultMessageListenerContainer.handleListenerSetupFailure():842
WARN ]: Setup of JMS message listener invoker failed for destination
'topic://check.newSecurityPublish' - trying to recover. Cause:
org.apache.activemq.ConnectionFailedException: The JMS connection has
failed: Connection refused

[ 2014-12-19 00:00:06,476 [securityEventDataSubscriberContainer-4105] 
listener.DefaultMessageListenerContainer.refreshConnectionUntilSuccessful():891
INFO ]: Successfully refreshed JMS Connection


Please note that we are seeing this only for one client and that too
sometimes. Other clients are able communicate with the broker properly.
Client is using pooledConnection factory to create the connection. 

Thanks,
Anuj



--
View this message in context: http://activemq.2283324.n4.nabble.com/After-broker-restart-subscirber-is-not-able-to-connect-tp4689171.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Mime
View raw message