[ https://issues.apache.org/activemq/browse/AMQ-836?page=all ]
james strachan resolved AMQ-836.
--------------------------------
Resolution: Fixed
You can now specify this on a property on the ActiveMQConnectionFactory POJO or
via a URI such as
tcp://localhost:61616?jms.clientIDPrefix=Cheese
> add a clientIDPrefix to ActiveMQConnectionFactory so that we can specify the
> prefix for any auto-generated clientIDs
> --------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-836
> URL: https://issues.apache.org/activemq/browse/AMQ-836
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker
> Reporter: james strachan
> Fix For: 4.1
>
>
> Its very useful to configure clientIDs on JMS connections for when browsing
> the status of a system via JMX...
> http://incubator.apache.org/activemq/jmx.html
> however the JMS specification only allows you to set the clientID for a
> *single* Connection. So in an application where you are using a
> ConnectionFactory to make multiple connection objects you cannot specify a
> client ID easily.
> So it would be good to allow a clientIDPrefix to be set which can then be
> appended with a counter/timestamp to ensure uniqueness - but at least it will
> start with a descriptive text in consoles etc
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
