Hi, I'm working with Websphere 5.1 and Websphere MQ Series 5.3.1 on Windows. I have a very simple hello world MDB that I've successfully deployed and run on Weblogic but have to manage to get running on Websphere. I have created a J2EE client ear file using the Application Server Toolkit. My MDB is already deployed and running. The server startup log shows no errors. However, my client can not retrieve reference to the QueueConnectionFactory. When I dump the server namespace I see the following: 6 (top)/jms/mdb.examples.QueueConnectionFactory 6 ERROR: Could not instantiate a bound object. 6 Bound Java type: javax.jms.QueueConnectionFactory 6 Local Java type: NULL 6 String representation:
7 (top)/jms/mdb.examples.messageQueue 7 Bound Java type: com.ibm.mq.jms.MQQueue 7 Local Java type: javax.naming.Reference 7 Corba binding type: org.omg.CosNaming.BindingType.nobject 7 String representation: Reference Class Name: com.ibm.mq.jms.MQQueue My queue is bound but not my connection factory. If I run my client (launchClient) using the dumpJavaNameSpace=true I see an entry 6 (top)/comp/env/jms/mdb.examples.QueueConnectionFactory though nothing for my queue. My client fails javax.naming.NameNotFoundException: Context: OPC129Network/nodes/OPC129/servers/nodeagent, name: jms/mdb.examples.QueueConnectionFactory: First component in name jms/mdb.examples.QueueConnectionFactory not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL mg.org/CosNaming/NamingContext/NotFound:1.0
This occurs when my client does a lookup of "java:comp/env/jms/mdb.examples.QueueConnectionFactory
Thanks, I had a look but no joy. I'm now having problems being told that comp/env/mdb.examples.QueueConnectionFactory" not found in context "java". As I launching the client using the Websphere launchClient command I would expect the classpath to be correct.