Hi again

Now I got a stacktrace, because obviously this problem is not related to
TcpTransport class at all, It just makes what It is designed to do, closing
the Connection is something for that TcpTransport class has no
responsibility. Here is the stack trace:

Daemon Thread [IdleRemover] (Suspended (breakpoint at line 519 in
TcpTransport))  
        TcpTransport.doStop(ServiceStopper) line: 519   
        TcpTransport(ServiceSupport).stop() line: 71    
        TcpTransport.stop() line: 577   
        InactivityMonitor(AbstractInactivityMonitor).stop() line: 147   
        WireFormatNegotiator(TransportFilter).stop() line: 65   
        WireFormatNegotiator.stop() line: 91    
        FailoverTransport.stop() line: 397      
        MutexTransport(TransportFilter).stop() line: 65 
        ResponseCorrelator(TransportFilter).stop() line: 65     
        ResponseCorrelator.stop() line: 132     
        ServiceSupport.dispose(Service) line: 43        
        ActiveMQConnection.close() line: 708    
        ActiveMQManagedConnection.destroy() line: 207   
        InternalManagedConnectionPool.doDestroy(ConnectionListener) line: 664   
        InternalManagedConnectionPool.removeIdleConnections() line: 483 
        IdleRemover$IdleRemoverRunnable.run() line: 171 
        Thread.run() line: 744  

Now It is time to look for candidates...



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker-tp4681005p4681083.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to