Posted: Thu May 08, 2008 3:17 am Post subject: Problems with WAS 6.0.2 and MQ 6
Newbie
Joined: 29 Apr 2008 Posts: 3
We are using WAS 6.0.2 and MQ v 6.0 installed on AIX box.
When we try to run any code that accesses MQ using base java we get the following error
Caused by: java.lang.NoSuchFieldError: msgToken
at com.ibm.mq.server.MQSESSION.init_conversion(Native Method)
at com.ibm.mq.server.MQSESSION.(MQSESSION.java:254)
at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:6
at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:493)
at com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:155)
at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnection(MQBin dingsManagedConnectionFactoryJ11.java:153)
at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnection(MQBind ingsManagedConnectionFactoryJ11.java:189)
at com.ibm.mq.StoredManagedConnection.(StoredManagedConnection.java:80)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManag er.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.(MQQueueManager.java:469)
I understand that this is a problem with WAS 6.0 because of older set of MQ jars and the solution is to change the MQ_INSTALL_ROOT to point to the MQ Installation dir.
However, there is a particular problem which we are not able to resolve. When we refresh the page, the error we get is different than what comes in the first time
java.lang.NoClassDefFoundError: com/ibm/mq/server/MQSESSION at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:6
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:417)
at sg.com.citibank.northstar.util.MQHelper.openManager(MQHelper.java:46)
at sg.com.citibank.northstar.components.testmq.testmq.FireMLI(testmq.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Is this error also related to the same problem.
We have kept the new com.ibm.mq.jar in the WEB-INF/lib folder of the application and also added the /usr/mqm/java/lib and all the jar to the classpath.
Can you check & make sure JMS server is running???
Talk to your WASAdmin. Usually you may see problems at WAS startup if JNDI is not configured right. Read the WAS manual about JMS Provider setup. _________________ MQ & Broker admin
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum