0 Replies Latest reply on Jun 10, 2014 3:46 PM by Vincent Crepin

    STOMP protocol activation brings container to halt

    Vincent Crepin Newbie



      I activated the stomp protocol on my activemq broker (by adding a transport connector).


      I have a route in a container that uses activemq using tcp. When I start the route, it establishes tcp and stomp connections to the broker and the container becomes irresponsive. The route cannot be deployed completely and the last entry in the log is :


      established connection to broker using stomp.


      I need to expose the stomp protocol for external clients to use activemq directly.


      Any ideas ?