Hi All,

I am working on project where MQ is used and the MDB is deployed on WAS 6. I have configured the queues, Queue managers, QCF and everything. I also created the Listeners for the respective MDB. I am able to deploy the application in WAS. When I tested the app with the dummy messages, I am getting the following error.
Your help or guidance is really appreciated....

[3/09/13 14:25:46:558 EST] 00000011 MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
[3/09/13 14:25:46:558 EST] 00000011 MDBListenerIm W WMSG0019E: Unable to start MDB Listener JMSEDAControllerMDB, JMSDestination jms/JMSConnectionFactoryRef : javax.naming.NameNotFoundException: Context: n304409Node01Cell/nodes/n304409Node01/servers/server1, name: jms/JMSConnectionFactoryRef: First component in name jms/JMSConnectionFactoryRef not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.handleNameNotFound(WsnOptimizedNamingImpl.java:2000)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.getNextWsnOptimizedNamingContext(WsnOptimizedNamingImpl.java:1321)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.getTargetContext(WsnOptimizedNamingImplBase.java:3024)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase$LeafOperationData.(WsnOptimizedNamingImplBase.java:3489)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:1427)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4045)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1776)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1737)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1444)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1324)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:229)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:680)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:653)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:962)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:90)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)
---- Begin backtrace for Nested Throwables
org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.handleNameNotFound(WsnOptimizedNamingImpl.java:2000)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.getNextWsnOptimizedNamingContext(WsnOptimizedNamingImpl.java:1321)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.getTargetContext(WsnOptimizedNamingImplBase.java:3024)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase$LeafOperationData.(WsnOptimizedNamingImplBase.java:3489)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:1427)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4045)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1776)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1737)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1444)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1324)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:229)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:680)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:653)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:962)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:90)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)

[3/09/13 14:25:46:574 EST] 00000011 MDBListenerIm I WMSG0058I: Listener Port searchRetrieveListener will attempt to restart in 60 seconds

 

Hi Anand,
 
  You are having a JNDI name problem.
 
  Review all JNDI names of your listener ports and QCF
 
  Connection factory JNDI name
   jms/JMSConnectionFactoryRef
   
    
  Take in mind that JNDI names a case sensitive, so both JNDI names need to be the same.  Review if you have any blank at the end of the JNDI name.
 
  Hope this helps.  Tell us if you need more support.
 
regards

Hi Gabriel,

Thanks for your reply.

I double-checked the JNDI names. Its same everywhere. There is no space after the name also. Even then, I am facing this issue. I tried to check if the JNDI is available in the servers,
1) Tried to create the same JNDI name and then the server did not allow me to create.-  which means it is there.
2) I also tried to execute the dumpNameSpace.bat file to see the list of JNDIs available in the server. I could not see as it gave me some error.

Can you please tell me how to see the list of JNDIs in the server through Admin console? Please let me know the other ways of fixing the issue

 

ok the problem is with your Queue Destination JNDI

Unable to start MDB Listener JMSEDAControllerMDB, JMSDestination jms/JMSConnectionFactoryRef : javax.naming.NameNotFoundException: Context: n304409Node01Cell/nodes/n304409Node01/servers/server1, name: jms/JMSConnectionFactoryRef

When you define a listener port you need to provide two names, one for the QCF and the other for the Queue.

  Connection factory JNDI name
    jms/JMSConnectionFactoryRef  -> your QCF JNDI
    
  Destination JNDI name
    jms/YOUR_QUEUE  -> your QUEUE JNDI

  You a putting in Destination JNDI name Connection factory JNDI name. An MDB read a queue using a connection factory to connect to queue.
    
test and let us know.

Regards

Hi,

Thanks for the clarification.

I should have mentioned about the JNDI and the Listener configurations in my original post.

Following are the JNDI names used in the listener.

QCF - jms/QueueManager
Destination -  jms/JMSConnectionFactoryRef

I should have given a different name to the Destination. jms/JMSConnectionFactoryRef is not the JNDI of QCF. Please let me know where I am missing.

Ok,

That is your configuration:

QCF - jms/QueueManager
Destination -  jms/JMSConnectionFactoryRef
 
And what is the scope (cell, node, server) of your Queue (jms/JMSConnectionFactoryRef)? where is defined?

Your MDB is looking at server level.

javax.naming.NameNotFoundException: Context: n304409Node01Cell/nodes/n304409Node01/servers/server1

regards

Initially, the QCF and Destinations were configured at the Node level. After your post, I changed the configuration of these to Server level and I deployed the app at the server level. Still I am getting the same error. 

[4/09/13 11:17:59:937 EST] 00000011 MDBListenerIm I WMSG0058I: Listener Port searchRetrieveListener will attempt to restart in 60 seconds
[4/09/13 11:18:59:951 EST] 0000000e MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
[4/09/13 11:18:59:967 EST] 0000000e MDBListenerIm W WMSG0019E: Unable to start MDB Listener JMSEDAControllerMDB, JMSDestination jms/JMSConnectionFactoryRef : javax.naming.NameNotFoundException: Context: nnab304409Node01Cell/nodes/nnab304409Node01/servers/server1, name: jms/JMSConnectionFactoryRef: First component in name JMSConnectionFactoryRef not found. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.do_resolve_complete_info(WsnOptimizedNamingImpl.java:969)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:1435)

Can you review in your SystemOut.log if jms/JMSConnectionFactoryRef is binding at the startup of the server? review too QCF, Listener Ports,... bindings.

You can find messages with CWWSR0049I code

ResourceMgrIm I   CWWSR0049I: Binding pru as jms/pr

I'm assuming that you haven't any problem at the startup of the server related to QCF, Listeners, Queues,...



regards

Hi Gabriel,

thanks for continuously helping...

I just checked the log file and I even restarted the server to check the QCF, Destination and Listener port entries. I dont find an entry with the code you mentioned. Also, the destination jms/JMSConnectionFactoryRef is giving the error during server startup (Error is same as the one - posted previously). The Listener port also has the startup error. PFB the error.


Is there a way to see the list of JNDIs in the server?

[4/09/13 17:41:33:333 EST] 00000027 MDBListenerIm I WMSG0058I: Listener Port searchRetrieveListener will attempt to restart in 60 seconds
[4/09/13 17:41:33:333 EST] 00000027 MsgListenerPo W WMSG0049E: Failed to start MDB JMSEDAControllerMDB against listener port searchRetrieveListener

 

OK the destination is giving and error and what type of error (put please)? the destination need to start ok if not the listener port can't bound. The MDB is the application and the last in start, all the resources need to be start without error.

You havent't any entry with word "Binding"?!?!? or you are talking about the Code? try the next code WSVR0049I

What WAS version do you have, 6.X? and OS?

Could you type:

  WAS_HOME\versionInfo
 

The only way I know is the utility dumpNameSpace

  WAS_HOME\bin\dumpNameSpace

but if the resource is not starting correctly, the JNDI name will fail.

Hi,

Im too facing same issue as reported here.. for WAS 6.0.2.x , AIX 5.3

The Listener ports cannot start due to Naming related errors in WAS log. The JMS configurations are defined at Node level, but the Naming exceptions point to the cluster level context and complains as Not found.

The issue popped up after the MQ Upgrade from v6 to v7. Not sure if they are related but theoretically I think no..

As per your comments i checked for dumpNameSpace at node and cell level... It did not show any jdbc / jms JNDI's.. It was listing only the URLs.

Is there a possibility of the Naming thing getting srewed up royally for a WAS server.. If so, what are the options before us..

Have read about Java/OS registries going bad which could affect Naming stuff.. Please advice