Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Received-SPF: pass (herse.apache.org: domain of teemu@torma.org designates
 213.41.244.89 as permitted sender)
From: Teemu Torma <teemu@torma.org>
To: dev@activemq.apache.org
Subject: ActiveMQ CPP connection factory behaviour
Date: Tue, 13 Mar 2007 10:50:15 +0100
User-Agent: KMail/1.9.4
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200703131050.15367.teemu@torma.org>

I was looking the connection factory in activemq-cpp (trunk version) to 
see why I can not create two connections using same factory due to 
client id clashes.

It appears that the connection factory creates only one uuid client id 
and uses it unless something else given to createConnection.  It also 
seems to cache the last given user/password and use them as default for 
the next connection too.

Intuitively I would think that defaults given to the constructor would 
be used unless something else was given to createConnection, and a 
unique client id would be generated each time unless something else was 
specified.

Is it like this by design or by accident?  Right now I see it really 
being usable for one connection only at least in my usage scenarios.  
It would be much more usable if user/password would not get sticky and 
client id would default to some kind of uuid + serial for each 
connection.

Teemu