I have a JMS-consumer (MDB) which consumes messages from a HornetQ-queue. When I call stopDelivery() from JMX-console, ObjectName=jboss.j2ee:jar=mock-reception.jar,name=FakeMQTestScenarioConsumer,service=EJB3, the client-connections are not closed (netstat shows state=ESTABLISHED) and they won't timeout either. Calling startDelivery() causes a new connection to be established. The result of this is leaking connections each time we start/stop delivery.
Is there a configuration-setting I can tune to avoid this connection-leak or does anybody knows what's going on?