Skip to main content

alphaWorks  >  Forums  >  IBM Client Application Tool for JMS  >  developerWorks

Connect Issue    Point your RSS reader here for a feed of the latest messages in this thread


     

 
 

My developerWorks
 Welcome, Guest
Sign in or register
Permlink Replies: 3 - Pages: 1 - Last Post: Nov 14, 2006 9:18 AM Last Post By: msmiths Threads: [ Previous | Next ]

Posts: 2
Registered: Oct 30, 2006 01:06:57 AM
Connect Issue
Posted: Nov 08, 2006 11:19:25 PM
Click to report abuse...   Click to reply to this thread Reply
I'm getting error (java.lang.NoSuchFieldError: msgToken) even though I clearly specify WMQ_JAR_PATH as the version of MQ used by the app server.

Any ideas?
msmiths

Posts: 5
Registered: Oct 04, 2006 02:56:16 AM
Re: Connect Issue
Posted: Nov 09, 2006 07:27:23 AM   in response to: in response to: 's post
Click to report abuse...   Click to reply to this thread Reply
Hi,

Off of the top of my head... no idea I'm afraid. Please could you provide more information about your environment, i.e., what version of WAS are you using, what version of WMQ are you using, what platform are you running on, what values are you specifying in the setenv script, what is the full stack trace of the exception?

If you can provide me with more information I can start looking into the problem.

Thanks.

Posts: 2
Registered: Oct 30, 2006 01:06:57 AM
Re: Connect Issue
Posted: Nov 12, 2006 10:41:19 PM   in response to: msmiths in response to: msmiths's post
Click to report abuse...   Click to reply to this thread Reply
Happy to provide more information if required. Thankyou for your assistance!

Websphere 6.02.13
Websphere MQ 6.0.1.1

set WAS_HOME=C:\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v6
set WMQ_JAR_PATH=C:\Program Files\IBM\WebSphere MQ\Java\lib

Full stack trace begins

java.lang.NoSuchFieldError: msgToken
at com.ibm.mq.server.MQSESSION.init_conversion(Native Method)
at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:254)
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(MQBindingsManagedConnectionFactoryJ
11.java:153)
at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnection(MQBindingsManagedConnectionFactoryJ1
1.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.createQMNonXA(MQConnection.java:1749)
at com.ibm.mq.jms.MQConnection.<init>(MQConnection.java:942)
at com.ibm.mq.jms.MQConnectionFactory.createConnection(MQConnectionFactory.java:3138)
at com.ibm.jms.client.util.JMSUtils.connect(JMSUtils.java:69)
at com.ibm.jms.client.swing.panel.JMSMessageConnectionPanel$ConnectionPanelActionListener.actionPerformed(JMSMes
sageConnectionPanel.java:656)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1815)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1868)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:449)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:287)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:274)
at java.awt.Component.processMouseEvent(Component.java:5196)
at java.awt.Component.processEvent(Component.java:4993)
at java.awt.Container.processEvent(Container.java:1607)
at java.awt.Component.dispatchEventImpl(Component.java:3712)
at java.awt.Container.dispatchEventImpl(Container.java:1665)
at java.awt.Component.dispatchEvent(Component.java(Inlined Compiled Code))
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java(Compiled Code))
at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3236)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3166)
at java.awt.Container.dispatchEventImpl(Container.java:1651)
at java.awt.Window.dispatchEventImpl(Window.java:1653)
at java.awt.Component.dispatchEvent(Component.java:3574)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:536)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:237)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:187)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:181)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:173)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:136)
msmiths

Posts: 5
Registered: Oct 04, 2006 02:56:16 AM
Re: Connect Issue
Posted: Nov 14, 2006 09:18:32 AM   in response to: in response to: 's post
Click to report abuse...   Click to reply to this thread Reply
Hi,

The problem appears to be a mismatch in the WMQ JARs that are being used on the client and server. This issue is discussed in the following technote:

http://www-1.ibm.com/support/docview.wss?uid=swg21221195

The suggested solution to this problem is to modify the <MQ_install_root> WebSphere environment variable to point at the JARs that ship with your WMQ installation.

Let me know if this fixes your problem.

Thanks.

Point your RSS reader here for a feed of the latest messages in all forums