Bug 705088

Summary: Concurrent connections to the same non-durable subscription with the same client ID should not be possible
Product: Red Hat Enterprise MRG Reporter: Pavel Moravec <pmoravec>
Component: qpid-javaAssignee: messaging-bugs <messaging-bugs>
Status: CLOSED DUPLICATE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: low Docs Contact:
Priority: unspecified    
Version: 1.3CC: rattapat+nobody
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-16 15:46:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Source files for replication none

Description Pavel Moravec 2011-05-16 15:26:29 UTC 
Description of problem:
Per JMS specification (http://www.oracle.com/technetwork/java/docs-136352.html
), the client state identified by a client identifier can be ‘in use’ by only one client at a time. However MRG allows more connections to the same non-durable subscription with the same client ID to be bound.


Version-Release number of selected component (if applicable):
MRG(M) 1.3

How reproducible:
Everytime: compile and run with junit the below test

Steps to Reproduce:
1. Untar attached source code
2. Compile both java files in src/com/gs/mrg/eval/ directory - it requires JUnit installed
3. Run: java org.junit.runner.JUnitCore ConnectionTest
  
Actual results:
"Failed to get exception" fail in ConnectionTest.java:38 is invoked - both connection1 and connection2 were created with the same client ID.

Expected results:
The fail should not be invoked and the test should pass.

Additional info:
Comment 1 Pavel Moravec 2011-05-16 15:27:37 UTC 
Created attachment 499187 [details]
Source files for replication
Comment 2 Rajith Attapattu 2011-05-16 15:46:22 UTC 

*** This bug has been marked as a duplicate of bug 704547 ***