Win a copy of 97 Things Every Java Programmer Should Know this week in the Java in General forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

Configuring WSAD5.1 with MQ5.2

 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I was using WSAD4.0 with MQ5.2 as the JMS provider.Recently we upgraded to WSAD5.1 but we have not upgraded the MQ version. We are still planning to use J2EE 1.2 and MQ 5.2 and NO MDBs but i am having difficulty configuring. Is there a document somewhere which tells how to configure between WSAD5.1.1 and MQ 5.2? I went through a lot of documents but all of them have MDBs and J2EE 1.3. I installed the embedded messaging client only. When i point my MQJMS_LIB to the MA88 package it gives me that field runninginWebsphere not found.
This is kind of urgent.We have to decide in a day or two if we can configure with this environment or we need to move back to WAS4.0?

Thanks in advance,
Tarun
 
Greenhorn
Posts: 22
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Read chapter 14 in ibm redbook SG24-6878-00: WebSphere Application
Server V5 and WebSphere MQ Family Integration
You must define a generic JMS provider not a Websphere MQ JMS provider in your Application server.
You can find in this book all what you need to configure your system
Mouloud
 
Tarun Bindal
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi samou,

Thanks for the prompt reply.I read that document and configured a generic JMS provider but now i get the following error --

[10/8/04 17:30:01:557 EDT] 3cc9c6cd ServletInstan E SRVE0100E: Did not realize init() exception thrown by servlet SigMessagingInitServlet: javax.servlet.ServletException: Can't find library mqjbnd05 (mqjbnd05.dll) in sun.boot.library.path or java.library.path
sun.boot.library.path=C:\IBM\WebSphere Studio\runtimes\base_v51\java\jre\bin
java.library.path=C:\IBM\WebSphere Studio\runtimes\base_v51/bin;C:\IBM\WebSphere Studio\runtimes\base_v51/java/bin;C:\IBM\WebSphere Studio\runtimes\base_v51/java/jre/bin;C:\IBM\WebSphere Studio\eclipse\jre\bin;.;C:\IBM\WebSphere Studio\eclipse\jre\bin;C:\Program Files\Perl\bin\;\\PVCS\PVCSAPPS\VM\win32\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program Files\SQLLIB\BIN;C:\Program Files\IBM\MQSeries\bin;C:\Program Files\IBM\MQSeries\tools\c\samples\bin;C:\IBM\MQSeries\Java\bin;C:\Program Files\Symantec\pcAnywhere;C:\IBM\WebSphere Studio\runtimes\base_v51\java\bin;C:\apache-ant-1.6.2\bin;C:\Program Files\GNU\WinCvs 1.3\CVSNT;c:\CommerceStudioEnhancements\bin
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doInit(StrictServletInstance.java:99)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._init(StrictLifecycleServlet.java:147)
at com.ibm.ws.webcontainer.servlet.PreInitializedServletState.init(StrictLifecycleServlet.java:270)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.init(StrictLifecycleServlet.java:113)
================

I have mqjbnd02.dll in the MA88 lib directory but not the 05 file.I searched for it but didn't find it anywhere.Do i need to install a patch on top of MA88 or something?

Thanks in advance,
Tarun
 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
WAS 5.1 comes with their own MQ libraries and may be messing things up.
Make sure the Generic JMS Provider points to the right MQ libraries and JMSAdmin is setup right.

I run my system on UNIX but i have noticed on Windows that there are System Variables that point to the WebSphere MQ libraries. Maybe point those to the ma88 libraries..
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm getting the same problem with that DLL. Anyone out there have any ideas? I don't see it even on my server that is running MQ client...
 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Could you please tell me the steps followed to fix this error.
I am stuck up in this for the last two days....
java.lang.UnsatisfiedLinkError: C:\Program Files\MQVE\mqjbnd05.dll: Can't find dependent libraries
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:2014)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1862)
at java.lang.Runtime.loadLibrary0(Runtime.java:823)
at java.lang.System.loadLibrary(System.java:885)
at com.ibm.mq.MQSESSION.loadLib(MQSESSION.java:865)
at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:227)
at java.security.AccessController.doPrivileged(Native Method)
at at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:221).null(Unknown Source)
at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:68)
at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:493)
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:155)
at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnection(MQBindingsManagedConnectionFactoryJ11.java:153)
at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnection(MQBindingsManagedConnectionFactoryJ11.java:189)
at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:80)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:171)
at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:754)
at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:688)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:469)
at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2248)
at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:1702)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:97)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:54)
at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46)
at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQXAQueueConnectionFactory.java:63)
at com.ibm.ejs.jms.JMSManagedQueueConnection.createConnection(JMSManagedQueueConnection.java:98)
at com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection.java:160)
at com.ibm.ejs.jms.JMSManagedQueueConnection.<init>(JMSManagedQueueConnection.java:64)
at com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory.createManagedConnection(WSJMSManagedQueueConnectionFactory.java:84)
at com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:477)
at com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1280)
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1064)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:1571)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:622)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:424)
at com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle.createQueueConnection(JMSQueueConnectionFactoryHandle.java:80)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:304)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:553)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:485)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListenerManagerImpl.java:443)
at com.ibm.ejs.jms.listener.MsgListenerPort.add(MsgListenerPort.java:152)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.startApplicationMDBs(MDBListenerManagerImpl.java:666)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.stateChanged(MDBListenerManagerImpl.java:637)
at com.ibm.ws.runtime.component.MessageListenerImpl.stateChanged(MessageListenerImpl.java:139)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged(ApplicationMgrImpl.java:388)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent(DeployedApplicationImpl.java:770)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:156)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:152)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:586)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:271)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:249)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:125)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:97)
 
But how did the elephant get like that? What did you do? I think all we can do now is read this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic