| Author |
Message
|
| tsrisudh |
 Posted: Tue Dec 13, 2005 7:28 am Post subject: [SOLVED]Listener Port issue |
 |
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
I have an MDB which i tested on my local WAS test environment and everything worked fine.
Noe i am trying to install the same on WAS 5.1.1.3 and the Listener ports are not starting
I get the following error
MDBListenerIm W WMSG0019E: Unable to start MDB Listener ValidateOrderMDB, JMSDestination jms/mq/ValidateQ : javax.nami
ng.NameNotFoundException: Context: specs-proto/nodes/specs-proto/servers/server1, name: jms/mq/ValidateQ: First component in name jms/mq/ValidateQ not foun
d. Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.handleNameNotFound(WsnOptimizedNamingImpl.java:1983)
at com.ibm.ws.naming.ipcos.WsnOptimizedNamingImpl.getNextWsnOptimizedNamingContext(WsnOptimizedNamingImpl.java:1320)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.getTargetContext(WsnOptimizedNamingImplBase.java:2500)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase$LeafOperationData.<init>(WsnOptimizedNamingImplBase.java:2965)
at com.ibm.ws.naming.cosbase.WsnOptimizedNamingImplBase.resolve_complete_info(WsnOptimizedNamingImplBase.java:1423)
at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(Unknown Source)
at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:3493)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1521)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1482)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1189)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1069)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:144)
at javax.naming.InitialContext.lookup(InitialContext.java:361)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:219)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:588)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:520)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListenerManagerImpl.java:482)
at com.ibm.ejs.jms.listener.MsgListenerPort.start(MsgListenerPort.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code))
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at com.tivoli.jmx.modelmbean.MMBInvoker.invoke(MMBInvoker.java:46)
at com.tivoli.jmx.modelmbean.MMBInvoker.invokeOperation(MMBInvoker.java:115)
at com.tivoli.jmx.modelmbean.DynamicModelMBeanSupport.invoke(DynamicModelMBeanSupport.java:409)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:323)
at com.tivoli.jmx.GenericMBeanSupport.invoke(GenericMBeanSupport.java:178)
at com.tivoli.jmx.MBeanAccess.invoke(MBeanAccess.java:113)
at com.tivoli.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:290)
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:659)
at com.ibm.ws.console.servermanagement.messagelistener.ListenerPortCollectionAction.perform(ListenerPortCollectionAction.java:272)
at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1791)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:510)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)
at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)
at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)
at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)
at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)
at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:1049)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:600)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:201)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:125)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:286)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:624)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:458)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:912)
I have seen other posts with similar problems and tried the following
Set MQ_INSTALL_ROOT to /usr/mqm
SET MQJMS_LIB_PATH to /usr/mqm/java/lib
restarted the server but still no luck
I did a dumpNameSpace but that does not have any reference to the q's or the q conn factory i defined in the server.
What is the mistake i am doing?
My env is
AIX
MQ 5.3
WAS 5.1.1.3
_________________
Srisudhir Tadepalli
Last edited by tsrisudh on Mon Dec 26, 2005 10:56 pm; edited 1 time in total |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Dec 13, 2005 7:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Stop the server.
rename or delete SystemOut.log.
Start the server.
Stop the server.
Open SystemOut.log in your favorite editor.
Read down the log from when the server initialized.
See if it says that your names were bound. It should explicitly report each name and thati t was bound successfully.
Find the *first* Error or Exception in the log, and post that.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| tsrisudh |
| Posted: Tue Dec 13, 2005 10:50 pm Post subject: |
|
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
I did what you specified and this is the first few lines
| Quote: |
The WebSphere MQ JMS Binders have been disabled as either the WebSphere MQ Client has not been installed, or the MQ_INSTALL_ROOT variable has not been set. |
I checked the WAS server and the server variable was actually set to /usr/mqm
So am lost now as to why WAS is not finding that variable?
_________________
Srisudhir Tadepalli |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Dec 14, 2005 4:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Do you have it set in the right context? Are you in an Dmgr setup, or a single server setup?
Does the user running WAS have security rights to /usr/mqm? Is it in the mqm group?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Dec 14, 2005 4:36 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
Well you need to check the right variable
Somewhere you will need to point to:
AIX: /usr/mqm/java/lib
Solaris:/opt/mqm/java/lib
Enjoy  |
|
| Back to top |
|
|
| tsrisudh |
| Posted: Wed Dec 14, 2005 4:46 am Post subject: |
|
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
Well i finally figured it out, the WAS admin had given me the wrong location of MQ, i have corrected that and now the binding happens fine, though am getting another issue
We have a queue which is defined in a MQ Server and the WAS has a queue manager which is in the cluster, now i am trying to get the MDB in the AIX box to listen to a cluster q.
This is my config for the QCF and q
QCF
Mapping-Configuration Alias : DefaultPrincipalMapping
Queue Manger name : CQM99 (This is the AIX cluster qmgr)
Trasport type : CLIENT
(Remaining default)
Queue
Base Q : MY.QUEUE
Host : empty
port empty
(Remaining default)
I get the following error, i looked up other similar messages but did not find a solution any idea what i am doing wrong?
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'specs-proto:FMCQM'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1450)
at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:915)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:118)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:77)
at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46)
at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQXAQueueConnectionFactory.java:53)
at com.ibm.ejs.jms.JMSManagedQueueConnection.createConnection(JMSManagedQueueConnection.java:118)
at com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection.java:189)
at com.ibm.ejs.jms.JMSManagedQueueConnection.<init>(JMSManagedQueueConnection.java:66)
at com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory.createManagedConnection(WSJMSManagedQueueConnectionFactory.java:92)
at com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:503)
at com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1331)
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1132)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:1747)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:711)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:464)
at com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle.createQueueConnection(JMSQueueConnectionFactoryHandle.java:80)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:308)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:588)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:520)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListenerManagerImpl.java:482)
at com.ibm.ejs.jms.listener.MsgListenerPort.add(MsgListenerPort.java:152)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.startApplicationMDBs(MDBListenerManagerImpl.java:715)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.stateChanged(MDBListenerManagerImpl.java:686)
at com.ibm.ws.runtime.component.MessageListenerImpl.stateChanged(MessageListenerImpl.java:151)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged(ApplicationMgrImpl.java:477)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent(DeployedApplicationImpl.java:791)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:157)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:153)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:589)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:301)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:258)
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:152)
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:243)
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:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5
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:189)
---- Begin backtrace for Nested Throwables
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2058
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:172)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:270)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:290)
at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.java:80)
at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConnectionManager.java:150)
at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:682)
at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:620)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:437)
at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1383)
at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:915)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:118)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:77)
at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46)
at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQXAQueueConnectionFactory.java:53)
at com.ibm.ejs.jms.JMSManagedQueueConnection.createConnection(JMSManagedQueueConnection.java:118)
at com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection.java:189)
at com.ibm.ejs.jms.JMSManagedQueueConnection.<init>(JMSManagedQueueConnection.java:66)
at com.ibm.ejs.jms.WSJMSManagedQueueConnectionFactory.createManagedConnection(WSJMSManagedQueueConnectionFactory.java:92)
at com.ibm.ejs.jms.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:503)
at com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper(FreePool.java:1331)
at com.ibm.ejs.j2c.poolmanager.FreePool.createOrWaitForConnection(FreePool.java:1132)
at com.ibm.ejs.j2c.poolmanager.PoolManager.reserve(PoolManager.java:1747)
at com.ibm.ejs.j2c.ConnectionManager.allocateMCWrapper(ConnectionManager.java:711)
at com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java:464)
at com.ibm.ejs.jms.JMSQueueConnectionFactoryHandle.createQueueConnection(JMSQueueConnectionFactoryHandle.java:80)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:308)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:588)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:520)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListenerManagerImpl.java:482)
at com.ibm.ejs.jms.listener.MsgListenerPort.add(MsgListenerPort.java:152)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.startApplicationMDBs(MDBListenerManagerImpl.java:715)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.stateChanged(MDBListenerManagerImpl.java:686)
at com.ibm.ws.runtime.component.MessageListenerImpl.stateChanged(MessageListenerImpl.java:151)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.stateChanged(ApplicationMgrImpl.java:477)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectEvent(DeployedApplicationImpl.java:791)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:157)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.setState(DeployedApplicationImpl.java:153)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:589)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:301)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:258)
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:152)
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:243)
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:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5
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:189)
_________________
Srisudhir Tadepalli
Last edited by tsrisudh on Wed Dec 14, 2005 4:51 am; edited 1 time in total |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Dec 14, 2005 4:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You are trying to do the impossible.
MDBs, like every other MQ application, can only listen to queues that are qlocal on the qmgr you are connected to.
A qcluster is not a qlocal. It is an alias to a qlocal somewhere.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| tsrisudh |
| Posted: Wed Dec 14, 2005 5:17 am Post subject: |
|
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
Well in that case how do i configure MDB if my MQ server is on different box than the WAS server?
_________________
Srisudhir Tadepalli |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Dec 14, 2005 5:42 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you have an MQServer on the WAS machine, then you can configure the qlocal on the qmgr there, and share it in the cluster so that other apps can put to it.
If you do not have an MQServer on the WAS machine, then you can configure the MDB to establish a client connection to the qmgr that has the qlocal (instead of just some server in the cluster).
But you won't get XA if you do this second one. Unless you're using the Extended Transactional Client.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| tsrisudh |
| Posted: Wed Dec 21, 2005 9:25 am Post subject: |
|
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
I configure the MDBs to have a client connection to the MQ server machine, but it still gives the same exception
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'specs-proto:FMCQM'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1450)
at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:915)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:118)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:77)
at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46)
at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQXAQueueConnectionFactory.java:53)
at com.ibm.ejs.jms.JMSManagedQueueConnection.createConnection(JMSManagedQueueConnection.java:118)
at com.ibm.ejs.jms.JMSManagedConnection.<init>(JMSManagedConnection.java
the specs-proto is my WAS machine, i am not sure why it is tring to create
queue on this machine
Any help
_________________
Srisudhir Tadepalli |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Dec 21, 2005 10:55 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
Did you uncheck the XA checkbox on the qcf setup ???
See your errorlog where it is trying to access an XA....
| Quote: |
| at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46) |
Enjoy |
|
| Back to top |
|
|
| tsrisudh |
| Posted: Fri Dec 23, 2005 2:58 am Post subject: |
|
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
I unchecked the XA box and restarted the server but still it is giving the same issue, no idea why it is still trying the same XA Connection
Is there any refresh i have to the WAS machine? I guess it is not taking hte latest configuration for whatever reason.
Any clues
_________________
Srisudhir Tadepalli |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Dec 23, 2005 11:47 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
You might have to go into the xml and change it there for it to hold.
Enjoy |
|
| Back to top |
|
|
| tsrisudh |
| Posted: Mon Dec 26, 2005 10:56 pm Post subject: |
|
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
Finally solved the issue, the issue was i had initially configured at the node level and changed to cell level, so whatever changes i made at the cel level were overriden by the node level.
I removed the config at the node level and everthing was fine
thanks to jefflowrey and fjb_saper for the help
_________________
Srisudhir Tadepalli |
|
| Back to top |
|
|
|
|
