Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-4847

STOMP logging does not work

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 9.0.2.Final, 10.0.0.Beta1
    • 9.0.0.CR2
    • None
    • None
    • Hide

      Shut down a STOMP client connection uncleanly, witness that nothing gets logged.

      Or try to connect with an unsupported STOMP version, for example:

      $ nc localhost 61613
CONNECT
accept-version:2.0

^@

      (nothing happens at this point, no response)

      Show
      Shut down a STOMP client connection uncleanly, witness that nothing gets logged. Or try to connect with an unsupported STOMP version, for example: $ nc localhost 61613 CONNECT accept-version:2.0 ^@ (nothing happens at this point, no response)
    • Hide

      Add org.jboss.logging module dependency to modules/system/layers/base/org/hornetq/protocol/stomp/main/module.xml

      Show
      Add org.jboss.logging module dependency to modules/system/layers/base/org/hornetq/protocol/stomp/main/module.xml

    Description

      STOMP errors do not get logged at all, for example "HQ222068: connection closed ..." on unclean connection close.

      Also, apparently due to the same root cause (or at least fixed by the same fix), for example connecting with an unsupported STOMP version just hangs instead of responding with the ERROR frame.

      Attachments

        Activity

          People

            jgreene@redhat.com Jason Greene
            vskytta_jira Ville Skyttä (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: