Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

problem when using MQ as JMS provider of WebSphere Application Server V6.0.1

31 views
Skip to first unread message

yipin...@hotmail.com

unread,
Nov 10, 2005, 9:41:12 PM11/10/05
to
I installed WebSphere MQ 6.0, and created Queue Manager and queue. Installed WebSphere Application Server V6.0.1, configured MQ Queue Topic Connection Factory & MQ Queue Topic, but when I deploy my application with MDB in it, I got: mbean exception: com.ibm,ws.exception. RuntimeError: java.lang.NoSuchFieldError: msgToken

David Currie

unread,
Nov 11, 2005, 8:31:42 AM11/11/05
to
Hi,

Is there a corresponding stack trace to indicate where the
NoSuchFieldError was coming from? Which MQ JMS JARs is your MQ JMS
provider configured to use?

Thanks,
David

yipin...@hotmail.com

unread,
Nov 11, 2005, 11:53:27 AM11/11/05
to
Here is the stack trace:

Caused by: 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(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:2238)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1739)
at com.ibm.mq.jms.MQTopicConnection.<init>(MQTopicConnection.java:171)
at com.ibm.mq.jms.MQTopicConnection.<init>(MQTopicConnection.java:84)
at com.ibm.mq.jms.MQXATopicConnection.<init>(MQXATopicConnection.java:47)
at com.ibm.mq.jms.MQXATopicConnectionFactory.createXATopicConnection(MQXATopicConnectionFactory.java:65)
at com.ibm.ejs.jms.JMSManagedTopicConnection.createConnection(JMSManagedTopicConnection.java:124)
at com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection.java:258)
at com.ibm.ejs.jms.JMSManagedTopicConnection.<init>(JMSManagedTopicConnection.java:72)
at com.ibm.ejs.jms.WSJMSManagedTopicConnectionFactory.createManagedConnection(WSJMSManagedTopicConnectionFactory.java:98)
at com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:582)
at com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1502)
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1294)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:2023)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:800)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:576)
at com.ibm.ejs.jms.JMSTopicConnectionFactoryHandle.createTopicConnection(JMSTopicConnectionFactoryHandle.java:81)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:418)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:681)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:612)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListenerManagerImpl.java:605)
at com.ibm.ejs.jms.listener.MsgListenerPort.add(MsgListenerPort.java:165)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.startApplicationMDBs(MDBListenerManagerImpl.java:828)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.stateChanged(MDBListenerManagerImpl.java:799)
at com.ibm.ws.runtime.component.MessageListenerImpl.stateChanged(MessageListenerImpl.java:140)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged(ApplicationMgrImpl.java:973)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent(DeployedApplicationImpl.java:1011)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:206)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:201)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:736)
... 40 more

yipin...@hotmail.com

unread,
Nov 11, 2005, 4:59:44 PM11/11/05
to
new error of the problem:

[11/11/05 14:36:09:750 EST] 0000000a ResourceMgrIm E WSVR0017E: Error encountered binding the J2EE resource, theTopicConnectionFactory, as jms/theTopicConnectionFactory from file:/D:/IBM/WebSphere/AppServer/profiles/default/config/cells/qaott11Node01Cell/nodes/qaott11Node01/resources.xml
com.ibm.ws.runtime.component.binder.ResourceBindingException: invalid configuration passed to resource binding logic. REASON: Failed to create connection factory: Error raised constructing AdminObject, error code: Transport Type : Transport Type
at com.ibm.ejs.jms.JMSConnectionFactoryReferenceable.<init>(JMSConnectionFactoryReferenceable.java:146)
at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.createNonGenericConnectionFactoryReferenceable(JMSResourceRefBuilderImpl.java:617)
at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.createNonGenericConnectionFactoryReferenceable(JMSResourceRefBuilderImpl.java:582)
at com.ibm.ejs.jms.JMSResourceRefBuilderImpl.createMQConnectionFactoryReferenceable(JMSResourceRefBuilderImpl.java:512)
at com.ibm.ws.runtime.component.binder.MQConnectionFactoryBinder.getBindingObject(MQConnectionFactoryBinder.java:193)
at com.ibm.ws.runtime.component.ResourceMgrImpl.bind(ResourceMgrImpl.java:320)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResourceProvider(ResourceMgrImpl.java:1019)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResource(ResourceMgrImpl.java:901)
at com.ibm.ws.runtime.component.ResourceMgrImpl.installResources(ResourceMgrImpl.java:841)
at com.ibm.ws.runtime.component.ResourceMgrImpl.loadResources(ResourceMgrImpl.java:670)
at com.ibm.ws.runtime.component.ResourceMgrImpl.start(ResourceMgrImpl.java:547)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:821)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:821)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:381)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:180)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:129)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:373)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)

David Currie

unread,
Nov 15, 2005, 6:00:21 AM11/15/05
to
Sorry - should have read your original post more carefull.

WAS 6.0.1 does not support WMQ 6:
http://www-306.ibm.com/software/webservers/appserv/doc/v60/prereqs/was_v601.htm

Please move to WAS 6.0.2:
http://www-306.ibm.com/software/webservers/appserv/doc/v60/prereqs/was_v602.htm

Regards,
David

David Currie

unread,
Nov 25, 2005, 9:27:22 AM11/25/05
to
In case anyone else happens to see this NoSuchFieldError, it indicates
that you are trying to perform a bindings connection. The WMQ JAR files
shipped with WAS are only sufficient to perform a client connection. For
a bindings connection you should modify the MQ_INSTALL_ROOT to point to
your WMQ installation (which you will have to have anyway for a bindings
connection).

Regards,
David

0 new messages