Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-1495

A-MQ Stomp connector sometimes log "WARN ProtocolConverter - Exception occurred processing: null : org.apache.activemq.transport.stomp.ProtocolException: Specified content-length is not a valid integer" without proper stacktrace

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • JBoss A-MQ 6.2.1
    • stomp
    • None

      When logging `org.apache.activemq.transport.stomp` sometimes A-MQ logs:

      2015-11-26 07:32:52,187 [ActiveMQ NIO Worker 7992] WARN ProtocolConverter - Exception occurred processing:
null

: org.apache.activemq.transport.stomp.ProtocolException: Specified content-length is not a valid integer

      Without a proper stacktrace or client connection information, making it difficult to track down the faulty client.

              Unassigned Unassigned
              rhn-support-iweiss Ingo Weiss
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: