Issue Details (XML | Word | Printable)

Key: GLASSFISH-17101
Type: Bug Bug
Status: Closed Closed
Resolution: Duplicate
Priority: Blocker Blocker
Assignee: Satish Kumar
Reporter: magnus12345678
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

JMS Connection Factory lookup failed with clustered JMS

Created: 25/Jul/11 03:01 PM   Updated: 26/Jul/11 08:45 AM   Resolved: 26/Jul/11 08:45 AM
Component/s: jms
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Environment:

Linux 64 bit, Glassfish 3.1 in cluster


Tags:
Participants: kumara, magnus12345678 and Satish Kumar


 Description  « Hide

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.



kumara added a comment - 25/Jul/11 05:18 PM

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


Satish Kumar added a comment - 26/Jul/11 08:45 AM

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