Maybe ActiveMQ inside JBoss isn't working well? I can't speak to it - I recommend against it.
ActiveMQ and JBoss are both heavy-weight. Of course, you could just mean ActiveMQ with wrappers as I believe that's what is branded as JBossMQ. Anyway, I wish I could help more - just don't have knowledge of JBoss here. One thing to comment - that log message is safe to ignore as both sides of the connection cleanup properly, but it does sound like - in this case - it's telling you something worth considering since dropped connections can lead to problems with ActiveMQ if the frequency gets high enough. In order to raise a bug with the community that is likely to get attention, it would be helpful to have a minimal use-case showing the problem with only ActiveMQ code. -- View this message in context: http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker-tp4681005p4681128.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
