| Author |
Message
|
| ckelly |
 Posted: Wed Jun 02, 2004 11:24 am Post subject: Unable to lookup JMS resources, JNDI lookup exception |
 |
|
Novice
Joined: 15 Nov 2002
Posts: 15
Location: London
|
Hi
I'm having a thoroughly horrible time trying to get WAS5.0.2 and MQ5.3 to talk to eachother on Solaris - Any assistance gratefully received!
I have configured the following in the WAS:
Set up my reference to the queue connection factory under >WebSphere MQ JMS Provider > WebSphere MQ Queue Connection Factories
Set up the q's under >WebSphere MQ JMS Provider > WebSphere MQ Queue Destinations
Set up the listener ports under >Application Servers > myserver > Message Listener Service > Listener Ports and made sure everything referenced is in the correct case.
Made sure the /opt/mqm/jave/lib/ .jar files are set in the classpath
Set up the qmgr on the same physical server.
When I start the server on the WAS I get the following errors:
[02/06/04 19:10:38:446 BST] 9f0d MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: <null>
[02/06/04 19:10:38:845 BST] 9f0d MDBListenerIm W WMSG0019E: Unable to start MDB Listener MessageRouterMDB, JMSDestination jms/MyQueue: javax.naming.NameNotFoundException: jms/MyQCF.XA. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound
[02/06/04 19:10:39:201 BST] 9f0d MsgListenerPo W WMSG0049E: Failed to start MDB MessageRouterMDB against listener port MyListPort
I did a dumpNameSpace, my q's were there but no reference to the Queue Connection Factory
Where am I going wrong?
Thanks in advance
CK |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Jun 02, 2004 11:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you define MQ_INSTALL_ROOT?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 02, 2004 11:31 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Can you post your MQ_JMS_ROOT variable as defined in WAS ?
Thanks
F.J. |
|
| Back to top |
|
|
| ckelly |
| Posted: Wed Jun 02, 2004 11:50 am Post subject: |
|
|
Novice
Joined: 15 Nov 2002
Posts: 15
Location: London
|
Hi
I haven't set either of these in the Manage Websphere Variables but I have set up in >Application Servers > MyServer > Process Definition > Java Virtual Machine > Custom Properties
ws.ext.dirs=/opt/mqm/java/lib/com.ibm.mqbind.jar
ws.ext.dirs=//opt/mqm/java/lib/com.ibm.mq.jar
ws.ext.dirs=//opt/mqm/java/lib/com.ibm.mqjms.jar
ws.ext.dirs=//opt/mqm/java/lib/ldap.jar
ws.ext.dirs=//opt/mqm/java/lib/providerutil.jar
and these are listed in the Start Display Current Environment in the systemOut log when the server starts.
I have a colleague who has got the same config on another server and QMgr and his works but niether of us can see a difference in config I have set up to cause my listeners to not start!
thanks |
|
| Back to top |
|
|
| ckelly |
| Posted: Wed Jun 02, 2004 11:52 am Post subject: |
|
|
Novice
Joined: 15 Nov 2002
Posts: 15
Location: London
|
| whoops didn't mean to have //opt should read /opt..... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 02, 2004 11:59 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
MQ_JMS_ROOT should usually be defined to a subdirectory of MQ_INSTALL_ROOT (like "{MQ_INSTALL_ROOT}/java/lib").
Try setting MQ_INSTALL_ROOT to /opt/mqm/, and restarting the server.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ckelly |
| Posted: Wed Jun 02, 2004 12:10 pm Post subject: |
|
|
Novice
Joined: 15 Nov 2002
Posts: 15
Location: London
|
Hi
I set MQ_INSTALL_ROOT=/opt/mqm and MQJMS_LIB_ROOT=$MQ_INSTALL_ROOT/java/lib and restarted the server but alas the same errors!
ck |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 02, 2004 12:18 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Did you define the names in the WebSphere MQ JMS Provider or the regular JMS provider?
Are there errors at the start of your log for your current startup - during the application server startup section before it loads any apps.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ckelly |
| Posted: Wed Jun 02, 2004 12:22 pm Post subject: |
|
|
Novice
Joined: 15 Nov 2002
Posts: 15
Location: London
|
I configured the names in WebSphere MQ JMS Provider.
There are no errors in the server startup before the app loads. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 02, 2004 12:33 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| ckelly wrote: |
I configured the names in WebSphere MQ JMS Provider.
There are no errors in the server startup before the app loads. |
Do you see it report that it bound the names?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ckelly |
| Posted: Thu Jun 03, 2004 7:39 am Post subject: |
|
|
Novice
Joined: 15 Nov 2002
Posts: 15
Location: London
|
No it's not getting that far as it isn't registering the queue connection factory in the jndi namespace.
I have deleted rverything bounced the server and reconfigured but to no avail. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jun 05, 2004 9:23 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Guys,
Read attentively the first page on the JMS MQ provider
and especially the explanation about what needs to be
in the JMS_MQ_ROOT variable:
Here an example: (read the code as one long line)
| Code: |
/opt/mqm/java/lib:/opt/mqm/java/lib/jdbc
:/opt/mqm/java/lib/com.ibm.mqjms.jar
:/opt/mqm/java/lib/com.ibm.mq.jar
:/opt/mqm/java/lib/com.ibm.mqbind.jar
:/opt/mqm/java/lib/connector.jar
:/opt/mqm/java/lib/jndi.jar |
and possibly some others I just forgot.
Any missing jar and there will be no set up of the resource.
Of course additionnally the setup of an alias for the connection to the manager (cmp managed...)
and the setup in MQ for the aforementioned alias with permissions +allmqi
for the queue manager and the queues would be highly recommended.
Have some fun.
F.J.  |
|
| Back to top |
|
|
| ckelly |
| Posted: Fri Jun 11, 2004 3:25 am Post subject: |
|
|
Novice
Joined: 15 Nov 2002
Posts: 15
Location: London
|
Eureka! Problem solved 
Just for completeness and if anyone else gets this problem they'll know.
The base level of Websphere Application Server I had installed was 5.02 with e-fix PQ76707 I changed the e-fix to PQ77263 and all listeners started.
Thanks to all those who replied to this post. |
|
| Back to top |
|
|
|
|
