[GLASSFISH-17101] JMS Connection Factory lookup failed with clustered JMS Created: 25/Jul/11  Updated: 26/Jul/11  Resolved: 26/Jul/11

Status: Closed
Project: glassfish
Component/s: jms
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: magnus12345678 Assignee: Satish Kumar
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux 64 bit, Glassfish 3.1 in cluster



 Description   

JMS Connection Factory lookup failed
Environment:
Clustered Glassfish 3.1 with JMS cluster(built-in OpenMQ)
JMS cluster setup:
JMS Availability : shareddb
Mode(EMBEDDED/LOCAL/REMOTE): LOCAL

Source code to get ConnectionFactory:
javax.naming.InitialContext jndi = new javax.naming.InitialContext();
ConnectionFactory qFactory = (ConnectionFactory) jndi.lookup("jms/queueConnectionFactory");

It seems jms/queueConnectionFactory is not available in the context.



 Comments   
Comment by kumara [ 25/Jul/11 ]

Please provide detailed steps to reproduce including how JMS cluster was configured and where/how the code segment is being run.

Comment by Satish Kumar [ 26/Jul/11 ]

This is a duplicate of 17099. Hence closing this issue.

Generated at Thu Sep 29 07:17:33 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.