Uploaded image for project: 'ActiveMQ Classic'
  1. ActiveMQ Classic
  2. AMQ-7068

Advisory messages are empty when received with a AMQP subscription

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 5.15.6
    • 5.15.11, 5.16.0
    • AMQP, Transport
    • None
    • ActiveMQ 5.15.6, JDK 1.8.0_161, Windows 10, AMQPNetLite 2.1.4

    Description

      We are currently moving from OpenWire to AMQP with .NET Library amqpnetlite (https://github.com/Azure/amqpnetlite) to communicate. So far most things work fine, but we actively used and need the advisory messages in order to recognize if other clients disconnect for example.

      Accessing the advisory messages through the topic is not the problem, but the body is null for the ActiveMQ.Advisory.Connection topic. There are some properties set, but no body set and I'm not able to find any important information, like the RemoveInfo. I attached a few screenshots from debugger.

      To be honest, I don't know if this is the desired behavior, but I think if there are messages on the advisory topic they should be useful.

      I know that a byte representation wouldn't be that useful, but you could present the information in json or xml format, like in Stomp? (https://issues.apache.org/jira/browse/AMQ-2098)

      Attachments

        1. issueamq2.PNG
          13 kB
          Johannes Baeurle
        2. issueamq.PNG
          21 kB
          Johannes Baeurle
        3. issueamq3.PNG
          24 kB
          Johannes Baeurle

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jbonofre Jean-Baptiste Onofré
            HNS90 Johannes Baeurle
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 10m
                10m

                Slack

                  Issue deployment