[MQ-270] Client ID value is not set correctly Created: 16/Jan/13  Updated: 18/Jan/13  Resolved: 18/Jan/13

Status: Closed
Project: mq
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Simon Meng Assignee: saradak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: jms-2-implementation

 Description   

CTS test(Client_checkClientIDOnDurableConnFactoryTest) failed at getting client id that is defined in the annotation for the
connection factory.

The test output file is at:
http://mq-hudson.us.oracle.com/job/mq-5.0-javaee7-cts-continuous/261/artifact/test_results/JTwork/com/sun/ts/tests/jms/ee20/resourcedefs/annotations/Client_check*

Test code is at: http://mq-hudson.us.oracle.com/job/mq-5.0-javaee7-cts-continuous/ws/javaeetck/src/com/sun/ts/tests/jms/ee20/resourcedefs/annotations/



 Comments   
Comment by Simon Meng [ 16/Jan/13 ]

It looks like com.sun.messaging.jms.ra.DirectConnectionFactory has problem. When using this class to create connection or context, it does not set the client ID attribute correctly.

Comment by Ed Bratt [ 17/Jan/13 ]

Please investigate

Comment by saradak [ 18/Jan/13 ]

This is a bug in CTS testcase.
It looks like CTS test is not closing the context after the appclient test is done. After that immediately calling servlet test which tries to create the context with the same clientid.

Generated at Fri Mar 06 04:59:13 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.