On 04/11/2013 11:14 AM, matteor wrote:
Dear all,
I would like to ask you why I'm experiencing a quite strange situation with
ActiveMQ 5.8.0.
I have a 5.8.0 AMQ broker with the following transport connectors:
As soon as I try connecting a CMS client to this broker (using SSL), I got
an out of memory error. The generated hprof shows that the activemq broker
instantiated 42 instances of org.apache.activemq.transport.nio.NIOTransport
class, each swallowing 369.295.688 bytes.
In total, the 42 instances of NIOTransport consume something like 2,9 GB.
Is the transport that you are connecting to a NIO connector or a NIO+SSL
connector?
Have you tested the connectivity between CMS and the plain SSL transport
connector first to ensure things work as expected?
I would like to understand why this huge amount of memory happens and how I
could limit the NIOTransport memory allocation (if this makes sense, of
course).
Thank you very much!
matteo
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Abnormal-NIOTransport-memory-usage-tp4665860.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/
