Details
Description
We need advisory messages for client connections, and we are stomp when connecting to ActiveMQ. When we subscribe to ActiveMQ.Advisory.Connection, we get messages when clients connect of disconnect, but the messages are empty. I suspect the information is lost when converting the ActiveMQMessage to a Stomp message.
Some sort of simple serialization (like key: value pairs) of the ConnectionInfo object in ActiveMQMessage.getDataStructure would solve the problem.
Attachments
Attachments
Issue Links
- is duplicated by
-
AMQ-5220 Advisory messages are still empty when received with a Stomp subscription
- Resolved