activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-797) Add client based advisory messages
Date Wed, 12 Oct 2016 16:39:20 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569188#comment-15569188
] 

Christopher L. Shannon commented on ARTEMIS-797:
------------------------------------------------

I can do a PR for this but want to first discuss the location for the advisory framework and
also the strategy for handling protocols that don't provide the notion of a producer.

> Add client based advisory messages
> ----------------------------------
>
>                 Key: ARTEMIS-797
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-797
>             Project: ActiveMQ Artemis
>          Issue Type: Sub-task
>          Components: Broker
>            Reporter: Christopher L. Shannon
>
> This task is for adding client based advisories (new connections, new consumers and new
producers).  Connections and consumers are straight forward but not all protocols tracker
producers.  With OpenWire and AMQP producers are tracked so this is easy.  STOMP and MQTT
do not track producers and ActiveMQ 5.x just handles this by sending a producer advisory for
any new connection.  We could also just not send producer advisories for STOMP/MQTT.
> For the CORE protocol, producers are not currently tracked but I think we should add
a new packet type so the broker can keep track of new producers and send advisories and keep
statistics.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message