Websphere 6.1 + MQ 6.0

[s_bu...@cat.com]

I'm trying to setup WAS 6.1 with MQ 6.0.x on windows and keep running into a variety of problems. First, I've changed the MQ_INSTALL_ROOT to point to the right MQ instance, when I do, I get the error below. I have full versions of MQ server and client installed, amqsputc works fine and I have the MQSERVER env variable set. Obviously my ultimate goal is to connect via BINDINGS bindings (not CLIENT).<br />
<br />
Caused by: javax.naming.NamingException: WMSG2001E: It was not possible to lookup the specified WebSphere MQ administered object because the WebSphere MQ client libraries are not available to the server.<br />
at com.ibm.ejs.jms.SubstituteJMSResourceObjectFactory.getObjectInstance(SubstituteJMSResourceObjectFactory.java:70)<br />
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:316)<br />
at com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpers.java:896)<br />
... 14 more<br />
<br />
Since this didn't work, I tried copying jars to the WMQ dir under the WAS isntall and changing the env. variable back. That got me past he above error, but now I get the error below. I have validated that the right directories (both Java/lib and bin from MQ) are indeed in teh PATH evn variable. I even tried coping the dll's to the same directory.<br />
Stack Dump = com.ibm.ws.exception.RuntimeError: java.lang.RuntimeException: java.lang.UnsatisfiedLinkError: mqjbnd05 (JVMPORT015E Unable to resolve DLL references - a prerequisite DLL may be missing)<br />
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:974)<br />
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2120)<br />
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:342)<br />
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1469)<br />
<br />
So since none of these worked, I changed back to CLIENT settings, using the copied jar files. That worked. <br />
<br />
My questions is ultimately, why doesn't WAS recognize the MQ_INSTALL_ROOT set to :c:\Program Files\IBM\MQ? And I have tried different slashes (\/), short DOS names (Progra~1) but nothing seems to work. Am I seting this wrong?<br />
<br />
Can someone HELP?<br />
<br />
Thanks in advance.

[Graham Hopkins]

Hi,

Could you try setting the MQ_INSTALL_ROOT to point to your native MQ
install, stop your server and then from the profile bin
directory run osgiCfgInit.bat and then restart the server. Hopefully when
you restart the server your JNDI objects should bind and
be usable in bindings mode

Regards

Graham

[Alasdair Nottingham]

Hi,<br />
<br />
The JNDI error you get is a symptom of the underlying problem. For some reason it has not been possible to obtain the WebSphere MQ client installed at the MQ_INSTALL_ROOT as a result rather than getting JNDI NameNotFoundExceptions we try to give you something more useful.<br />
<br />
If you restart the server with MQ_INSTALL_ROOT pointing at the WebSphere MQ location and then look at the server logs you should see the error message in the first 10 or so lines of output. I suggest you search the file for messages starting with WMSG. This should give you an error message with the problem the server found. If that does not help post it in here and we can see if anything obvious jumps out.<br />
<br />
Alasdair

[bshah]

I know websphere 6.1 comes with jar(mqm.jar...i think) which are
associated with MQ 5.0.x environment. Try changing the Environmental
Variable from within websphere especially the MQM_LIB Path?

Thanks
bshah