You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2018/10/08 12:03:00 UTC
[jira] [Commented] (AMQ-7068) Advisory messages are empty when
received with a AMQP subscription
[ https://issues.apache.org/jira/browse/AMQ-7068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641728#comment-16641728 ]
Timothy Bish commented on AMQ-7068:
-----------------------------------
Representing the OpenWire protocol objects in the AMQP body requires some work to produce conversions of the data into some types that can be marshalled in the AMQP protocol's type system. Currently no proper mapping has been done but if you want to contribute it we'd be happy to accept the patches. You'd likely need to convert the types into Map representations for the broadest comparability, XML would work but would be harder for folks to deal with than a simple mapping.
> 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)