2 Replies Latest reply on May 19, 2014 11:38 AM by Sanketi Mehta

    Jboss EAP 6.2 Stomp support

    Sanketi Mehta Newbie

      I migrated from Jboss AS 7.1.1 to Jboss EAP 6.2 recently. A remote client connects to a JMS Topic on both these Jboss servers using stomp protocol. I have provided stomp acceptor and required username, password, role for this client on Jboss AS 7.1.1 and same configuration on Jboss EAP 6.2. I have also granted appropriate permissions to this user in standalone xml.


      See below for details:

      <acceptor name="stomp-acceptor">
        
      <factory-class>org.hornetq.core.remoting.impl.netty.NettyAcceptorFactory</factory-class>
        
      <param key="host" value="<hostname>"/>
        
      <param key="protocol" value="stomp"/>
        
      <param key="port" value="61613"/>
       
      </acceptor>


      <security-setting match="#">
        
      <permission type="send" roles="admin, guest"/>
        
      <permission type="consume" roles="admin, guest"/>
        
      <permission type="createNonDurableQueue" roles="admin, guest"/>
        
      <permission type="deleteNonDurableQueue" roles="admin, guest"/>
        
      <permission type="createDurableQueue" roles="admin, guest"/>
        
      <permission type="deleteDurableQueue" roles="admin, guest"/>
      </security-setting>


      On AS 7.1.1, the client can consume messages just fine but on EAP 6.2 when client consumes messages, messages get stuck in-delivery state. On Management console, the topic continuously shows non-zero message count for in-flight messages.

      Can someone please provide any clue as to why this can happen? Does EAP 6.2 require any different configuration than AS 7.1.1.

      I have gone through Jboss HornetQ manual but so far have not found a solutionhttp://docs.jboss.org/hornetq/2.2.14.Final/user-manual/en/html_single/#stomp

      Thanks for your help.