[jira] Resolved: (AMQ-288) Allow the RA do customize the clientID using a clientID prefix then a counter after that for each connection it creates.

["Hiram Chirino (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQ-288?page=all ]
     
Hiram Chirino resolved AMQ-288:
-------------------------------

    Resolution: Won't Fix

It does not look like there is much interest in changing how the RA does client id handling.  The issue really did not make much sense to me.

> Allow the RA do customize the clientID using a clientID prefix then a counter after that for each connection it creates.
> ------------------------------------------------------------------------------------------------------------------------
>
>          Key: AMQ-288
>          URL: https://issues.apache.org/activemq/browse/AMQ-288
>      Project: ActiveMQ
>         Type: New Feature

>   Components: Connector
>     Reporter: james strachan

>
>
> enhance the RA to have a clientIDPrefix property in the ActiveMQConnectionRequestInfo class (with a similar getter/setter on the RA class too) so that you could specify your own clientID prefix - then the RA/MC could create a new client ID for each connection it makes by appending 1, 2, 3, 4 to the clientID.
> more background...
> On 6 Jul 2005, at 09:44, Roos, Robin wrote:
> Hi All
> I set the clientid element in ra.xml, but when I started the JBoss server with this deployment the ActiveMQ connection pool tried to create multiple connections with the same clientid.  Naturally that failed.
>   <config-property>
>   <description>The client id that will be set on the connection that is established to the ActiveMQ server.</description>
>   <config-property-name>Clientid</config-property-name>
>   <config-property-type>java.lang.String</config-property-type>
>   <config-property-value>GenesisApplicationServer</config-property-value>
>    </config-property>
> I was hoping that I could differentiate between different clients when reviewing activemq.log.  I set the clientid to "GenesisApplicationServer".  With a pooling policy it would be convenient if the connections in the pool became known as "GenesisApplicationServer-n" where n is the instance number in the pool.  But perhaps setting clientid is inappropriate in this case....
> Files activemq3.log and ra.xml are attached.
> Kind regards, Robin.

-- 
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