[
https://issues.apache.org/jira/browse/ARTEMIS-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15767033#comment-15767033
]
clebert suconic commented on ARTEMIS-796:
-----------------------------------------
Producer is a client's object. Some protocols will inform the server the server
when a producer was created.. some won't. (MQTT for instance won't as far as I
remember).
We can certainly add events for producer created on existing protocols, and
extend the Management events for that on the protocols that will support it,
but i wouldn't change core for that... as that will only bring a massive task
in place with little benefit beyond showing when an event, that could be
replaced by when the first message is sent.
I will close this JIRA since we have management in place at Artemis, and I
don't think we should implement the exact same API, as I said I'm more
interested in investing the time on new things...
Feel free to open the management event for created producers JIRA (on the
existing protocols).
> Add support for advisory messages
> ---------------------------------
>
> Key: ARTEMIS-796
> URL: https://issues.apache.org/jira/browse/ARTEMIS-796
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: Broker
> Reporter: Christopher L. Shannon
>
> ActiveMQ 5.x supports several advisory messages that are sent when certain
> events happen in the broker. They are described here:
> http://activemq.apache.org/advisory-message.html
> I am proposing that we provide the same advisory messages as described in the
> above documentation. These advisory messages provide a lot of useful
> information for monitoring what is going on with the broker in real time.
> One issue to work out is the protocol to use for the Advisory messages. A
> couple advisory messages are already being sent by the
> OpenWireProtocolManager for OpenWire clients but it may make more sense to
> send these messages at a more central location as the CORE protocol and then
> they can be converted to the correct type of message depending on the client.
> Sub tasks can be created for the different types of advisory messages that
> need to be added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
