[
http://jira.jboss.com/jira/browse/JBMESSAGING-826?page=comments#action_12... ]
Clebert Suconic commented on JBMESSAGING-826:
---------------------------------------------
The problem was when a PreConfgiuredClientID was in use, the same instance used to the
pre-configured clientID of the ConnectionFactory was changed... so a pre-configured user
used an attribute instead of a local method variable.
Using Pre Configure clientIDs will invalidate the usage of a simple
createConnection
------------------------------------------------------------------------------------
Key: JBMESSAGING-826
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-826
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.Beta1, 1.2.0.Beta2
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Blocker
Fix For: 1.2.0.CR1
Using a cf.createConnection(User,Password) for a user with a pre-configured clientID will
invalidate the use of cf.createConnection(); Something is dirty on the session keeping the
clientID from the previous invocation.
DuplicateClientIDTest::testNotDuplicateClientID fails for this.
This is the failing scenario:
c0 = cf.createConnection("dilbert", "dogbert");
c1 = cf.createConnection();
c1 can't be created as the CF will use the same pre-configured ID from dilbert.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira