I am using version 5.5.0 and after connecting 1000 clients with nio transport
connector, clients start to disconnect with the exception:

 15:24:11,307  WARN FailoverTransport:231 - Transport (null) failed to
nio://server2:61618 , attempting to automatically reconnect due to:
 org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too (>30000) long: server2/192.168.5.192:61618 [{InactivityMonitor Async
Task: java.util.concurrent.ThreadPoolExecutor$Worker@2083fc73}]

And in  the server I am getting these INFO messages:

17:14:46.808 [ActiveMQ NIO Worker] INFO  o.a.a.broker.TransportConnection -
The connection to 'null' is taking a long time to shutdown.

after querying a heap dump using Eclipse Memory Analyzer. 
Leak Suspects reports:

1,893 instances of
"org.apache.activemq.broker.region.cursors.FilePendingMessageCursor", loaded
by "org.apache.activemq.activemq-core" occupy 502,260,984 (68.64%) bytes.
These instances are referenced from one instance of "java.lang.Object[]",
loaded by "<system class loader>"

Keywords
java.lang.Object[]
org.apache.activemq.broker.region.cursors.FilePendingMessageCursor
org.apache.activemq.activemq-core


I seems that although I am using nio each connection is consuming a lot of
memory.

How can I reduce memory consumption ?

--
View this message in context: 
http://activemq.2283324.n4.nabble.com/clients-are-getting-disconnected-tp3999308p3999308.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to