[
https://issues.apache.org/jira/browse/AMQ-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16642839#comment-16642839
]
Johannes Baeurle commented on AMQ-7068:
---------------------------------------
Wow, thanks for the quick answer and for correcting the issue! I'd be happy if
I can contribute, as we would be very happy about that feature. I've seen there
is a activemq mirror on github, do you also accept pull requests there or just
patches in here?
> Advisory messages are empty when received with a AMQP subscription
> ------------------------------------------------------------------
>
> Key: AMQ-7068
> URL: https://issues.apache.org/jira/browse/AMQ-7068
> Project: ActiveMQ
> Issue Type: New Feature
> Components: AMQP, Transport
> Affects Versions: 5.15.6
> Environment: ActiveMQ 5.15.6, JDK 1.8.0_161, Windows 10, AMQPNetLite
> 2.1.4
> Reporter: Johannes Baeurle
> Priority: Minor
> Attachments: issueamq.PNG, issueamq2.PNG, issueamq3.PNG
>
>
> 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)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
