The transport I'm connecting to is a NIO+SSL one. I tried to specify a pure SSL transport at the broker side but I got the following exception
But I suspect that this is another story/problem: I have always used a NIO+SSL connector and it is ages since I last tried the pure SSL one. By the way, with activemq 5.6.0, the very same CMS client used to work correctly (no abnormal memory usage at the broker side). The connection string at the c# peer is Thank you very much, matteo -- View this message in context: http://activemq.2283324.n4.nabble.com/Abnormal-NIOTransport-memory-usage-tp4665860p4665878.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
