activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim van der Riet (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-447) broker doesn't sepcify any connection properties
Date Mon, 09 May 2016 15:05:13 GMT


Kim van der Riet commented on ARTEMIS-447:

For comparison, the following strings are returned by other related brokers (as read by a
Python client):

{symbol(u'platform'): u'Linux',
 symbol(u'product'): u'qpid-cpp',
 symbol(u'version'): u'0.35',
 symbol(u'host'): u'localhost.localdomain'}

*Active-MQ 5:*
{symbol(u'platform'): u'Java/1.8.0_65',
 symbol(u'product'): u'ActiveMQ',
 symbol(u'queue-prefix'): u'queue://',
 symbol(u'topic-prefix'): u'topic://',
 symbol(u'version'): u'5.12.0'}

|*platform*|version of Java|OS version|
|*host*|_<not supported>_|broker URL|
|*queue-prefix*|"queue://"|_<not supported>_|
|*topic-prefix*|"topic://"|_<not supported>_|

At a minimum, I would suggest that the *product* and *version* strings be set, as this is
what most clients would be looking for when trying to identify the broker.

> broker doesn't sepcify any connection properties
> ------------------------------------------------
>                 Key: ARTEMIS-447
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 1.3.0
>            Reporter: Gordon Sim
> When connecting to Artemis over AMQP, the broker doesn't send any properties in the connection
open frame that could be used to identify the broker as Artemis. This is a very useful feature
for debugging, and also vital if any application needs to be able to use special codepaths
when connected to Artemis (e.g. management related).

This message was sent by Atlassian JIRA

View raw message