MQSeries.net :: View topic - How to configure JMS/JTA between MQ V5.3 and WAS V4.0?

loris

Hi, All,

I use MQ V5.3 and I configure the JNDI in JMSAdmin.config like this:

INITIAL_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory
PROVIDER_URL=iiop://localhost/

When I run JMSAdmin.bat, the following error reports:

Exception in thread "P=794928:O=0:CT" java.lang.VerifyError: (class: com/ibm/ejs/ras/RasCo
ntextSupport, method: client_unmarshalled_request signature: (Lcom/ibm/CORBA/iiop/RequestH
older;)V) Incompatible object argument for method call
at com.ibm.ejs.ras.TraceEvent.<init>(TraceEvent.java:612)
at com.ibm.ejs.ras.TraceEvent.<init>(TraceEvent.java:548)
at com.ibm.ejs.ras.TraceEventGeneratorImpl.fireTraceEvent(Tr.java:1345)
at com.ibm.ejs.ras.Tr.warning(Tr.java:1082)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getCosRootContext(WsnInitCtxFactory.ja
va:488)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.j
ava:337)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContext(WsnInitCtxFactory.ja
va:200)
at com.ibm.websphere.naming.WsnInitialContextFactory.getInitialContext(WsnInitialC
ontextFactory.java:80)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:674)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:255)
at javax.naming.InitialContext.init(InitialContext.java:231)
at javax.naming.InitialContext.<init>(InitialContext.java:207)
at com.ibm.mq.jms.admin.AdminService.initJNDI(AdminService.java:188)
at com.ibm.mq.jms.admin.JMSAdmin.<init>(JMSAdmin.java:228)
at com.ibm.mq.jms.admin.JMSAdmin.main(JMSAdmin.java:1844)
D:\Program Files\IBM\WebSphere MQ\Java\bin>

My question is how to configure JMS/JTA between MQ V5.3(NOT V5.2) and WAS V4.0? I ever find documents on V5.2 to WAS V4.0, I want to know how to do with V5.3.

Thank you very much!
Loris