4 Replies Latest reply on Jun 21, 2011 4:37 AM by mbunzel

    STOMP ACK error messages

    mbunzel Newbie

      When using the STOMP protocol, a completely unexpected ACK message causes a NullPointerException to be returned. The minimal test case consists of  connecting (with our without client-id header), followed by sending an ACK message with an arbitrary message-id. The returned ERROR message looks like this:

       

      ERROR
      message:null
      content-length:1636
      
      java.lang.NullPointerException
              at org.hornetq.core.protocol.stomp.StompSession.acknowledge(StompSession.java:174)
              at org.hornetq.core.protocol.stomp.StompProtocolManager.onAck(StompProtocolManager.java:402)
              at org.hornetq.core.protocol.stomp.StompProtocolManager.handleBuffer(StompProtocolManager.java:203)
              at org.hornetq.core.protocol.stomp.StompConnection.bufferReceived(StompConnection.java:269)
              at org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:459)
      [...]
      

       

      Is this an expected behavior or should I open a JIRA issue?

       

      Another thing that I find curious is that when a large number of unexpected ACKs are sent, the exception (STOMP ERROR frame and logged to stdout) is shortened to:

       

      ERROR
      message:null
      content-length:31
      
      java.lang.NullPointerException
      

       

      This appears to persist until HornetQ is restarted. Is this an intentional behavior to prevent log spamming? Is there any way I can turn it off during dev/testing?

       

      Many thanks for such a great product,

       

      Mike