Grupos de Google ya no admite nuevas publicaciones ni suscripciones de Usenet. El contenido anterior sigue siendo visible.
Dismiss

Listener Port Start Problem, when integrating on WAS6.0 using Websphere MQ Publisher Subscriber

Visto 56 veces
Saltar al primer mensaje no leído

sk76_n...@hotmail.com

no leída,
29 jul 2005, 9:50:0829/7/05
a
Listener Port Start Problem, when integrating on WAS6.0 using Websphere MQ Publisher Subscriber
---------------------------
1)Websphere MQ is installed and top of that Publisher/subscriber support pack is also installed.
2)RAD6.0 with WAS6.0 is installed.
3)Aim: To run a MDB on WAS6.0 using Websphere MQ as JMS Provider.
4)Configured the item as specified at (MDB using MQ and WAS with RAD)
http://www-128.ibm.com/developerworks/websphere/techjournal/0505_woolf/0505_woolf.html
5)Below is the error message displayed onto the server console....

[7/29/05 12:08:43:125 IST] 0000001b MDBListenerIm I WMSG0058I: Listener Port JMSExampleTopicPort will attempt to restart in 60 seconds
[7/29/05 12:08:43:125 IST] 00000032 MDBListenerIm I WMSG0058I: Listener Port JMSExampleTopicPort will attempt to restart in 60 seconds
[7/29/05 12:08:43:141 IST] 0000001b MsgListenerPo W WMSG0049E: Failed to start MDB SubscriberDMDB against listener port JMSExampleTopicPort
[7/29/05 12:08:43:359 IST] 0000001b MDBListenerIm I WMSG0042I: MDB Listener JMSExampleQueuePort started successfully for JMSDestination jms/JMSExampleQueue
[7/29/05 12:09:43:219 IST] 0000002c ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource jms/JMSExampleConnectionFactory. The exception which was received is javax.jms.JMSException: MQJMS2008: failed to open MQ queue
[7/29/05 12:09:43:266 IST] 0000002c WASLogger E CLASSNAME METHODNAME an internal error has occurred. Please contact your system administrator. Detail: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2019
[7/29/05 12:09:43:266 IST] 00000036 JMSExceptionL E WMSG0018E: Error on JMSConnection for MDB SubscriberDMDB , JMSDestination jms/JMSExampleTopic : javax.jms.JMSException: MQJMS2008: failed to open MQ queue

[7/29/05 12:17:03:703 IST] 0000004b ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource jms/JMSExampleConnectionFactory. The exception which was received is javax.jms.JMSException: MQJMS2008: failed to open MQ queue
[7/29/05 12:17:03:719 IST] 0000004b WASLogger E CLASSNAME METHODNAME an internal error has occurred. Please contact your system administrator. Detail: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2019
[7/29/05 12:17:03:719 IST] 00000056 JMSExceptionL E WMSG0018E: Error on JMSConnection for MDB SubscriberDMDB , JMSDestination jms/JMSExampleTopic : javax.jms.JMSException: MQJMS2008: failed to open MQ queue
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:553)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2546)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2747)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessage(MQBrokerSubscriptionEngine.java:2785)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.openDurableSubscription(MQBrokerSubscriptionEngine.java:888)
at com.ibm.mq.jms.MQMigrateSubscriptionEngine.openDurableSubscription(MQMigrateSubscriptionEngine.java:544)
at com.ibm.mq.jms.MQConnectionBrowser.pubSubSetup(MQConnectionBrowser.java:400)
at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:266)
at com.ibm.mq.jms.MQConnectionBrowser.<init>(MQConnectionBrowser.java:143)
at com.ibm.mq.jms.MQConnection.createDurableConnectionBrowser(MQConnection.java:3438)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:463)
at com.ibm.mq.jms.MQConnection.createDurableConnectionConsumer(MQConnection.java:3349)
at com.ibm.mq.jms.MQXAConnection.createDurableConnectionConsumer(MQXAConnection.java:328)
at com.ibm.ejs.jms.JMSConnectionHandle.createDurableConnectionConsumer(JMSConnectionHandle.java:1016)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:509)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:680)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:611)
at com.ibm.ejs.jms.listener.MDBListenerManagerImpl.start(MDBListenerManagerImpl.java:605)
at com.ibm.ejs.jms.listener.MsgListenerPort.start(MsgListenerPort.java:250)
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(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1366)
at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:1012)
at mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(InvokerMBeanServerInterceptor.java:233)
at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:128)
at mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(SecurityMBeanServerInterceptor.java:86)
at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:128)
at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:128)
at mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.invoke(ContextClassLoaderMBeanServerInterceptor.java:167)
at mx4j.server.MX4JMBeanServer.invoke(MX4JMBeanServer.java:1249)
at com.ibm.ws.management.AdminServiceImpl$1.run(AdminServiceImpl.java:901)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.ibm.ws.management.AdminServiceImpl.invoke(AdminServiceImpl.java:817)
at com.ibm.ws.console.servermanagement.messagelistener.ListenerPortCollectionAction.execute(ListenerPortCollectionAction.java:317)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:275)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1486)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:528)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1212)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:629)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:80)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1657)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:77)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:421)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:367)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:94)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete(WorkQueueManager.java:548)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO(WorkQueueManager.java:601)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun(WorkQueueManager.java:934)
at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run(WorkQueueManager.java:1021)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)


6)in JMSAdmin.config file the propertied used are :
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
PROVIDER_URL=file:C:/JNDI-Directory

Help in resolving this is appreciated.
Thanx in Advance,
Sanjeev Kumar

p Lall

no leída,
29 jul 2005, 16:32:1529/7/05
a

Check out:
http://submit.boulder.ibm.com/dd/wsdd/asis/502019/502019.html

Don't forget to define your SIB and JMS resources in WAS - destinations, etc

<sk76_n...@hotmail.com> wrote in message
news:746575774.1122645039...@ltsgwas007.sby.ibm.com...

Paul Ilechko

no leída,
29 jul 2005, 16:58:1029/7/05
a
p Lall wrote:

> Check out:
> http://submit.boulder.ibm.com/dd/wsdd/asis/502019/502019.html
>
> Don't forget to define your SIB and JMS resources in WAS - destinations, etc

He's using WAS MQ as the JMS provider, not SIB ...

S31...@emirates.com

no leída,
31 jul 2005, 3:57:1831/7/05
a
http://www-128.ibm.com/developerworks/websphere/techjournal/0504_reinitz/0504_reinitz.html

sk76_n...@hotmail.com

no leída,
1 ago 2005, 1:44:331/8/05
a
As said by Paul Ilechko, SIB/ESB is NOT supported by Websphere MQ, basically we need to resolve this using the listener port as used in MQ configuration with WAS6/5 for MDB as listener.

Hence the link http://www-128.ibm.com/developerworks/websphere/techjournal/0504_reinitz/0504_reinitz.html is not the right solution i think, as this is ment for "DEFAULT Messaging" jms Provider but not for WebSphere MQ.
Plz., correct me if i am wrong :-).

Help in this regard is much appreciated.
thx
-Sanjeev

Paul Ilechko

no leída,
1 ago 2005, 9:42:361/8/05
a
sk76_n...@hotmail.com wrote:


Actually, it appears that your listener port is fine, but the resource
adapter is reporting a problem trying to open the destination
jms/JMSExampleTopic.

Look at this message closely:

> [7/29/05 12:09:43:266 IST] 00000036 JMSExceptionL E WMSG0018E: Error
> on JMSConnection for MDB SubscriberDMDB , JMSDestination
> jms/JMSExampleTopic : javax.jms.JMSException: MQJMS2008: failed to
> open MQ queue

You have a resource called JMSExampleTopic, but it's trying to open a
queue ....

Check your definitions closely. Also, make sure the pubsub fixpack
installed correctly, there should be logs.

p Lall

no leída,
1 ago 2005, 13:01:211/8/05
a
Great Catch

"Paul Ilechko" <paul.i...@us.ibm.com> wrote in message
news:dcl8sh$3se0$1...@news.boulder.ibm.com...

sk76_n...@hotmail.com

no leída,
2 ago 2005, 11:22:182/8/05
a
Listener Port Start Problem, when integrating on WAS6.0 using Websphere MQ Publisher Subscriber-2
*************************************************************************************************
1)Websphere MQ6.0(trial version) is installed on machine-1.
2)RAD6.0 with WAS6.0 is installed again on machine-1.
3)Aim: To run a MDB on WAS6.0 using Websphere MQ as JMS Provider for Publisher/Subscriber application.

4)Configured the item as specified at (MDB using MQ and WAS with RAD)
[change is instead of Webspher MQ5.3 Webspher MQ6.0 trial is used with embded publisher/subscriber support]
http://www-128.ibm.com/developerworks/websphere/techjournal/0505_woolf/0505_woolf.html

5)Listener Port for Queue is set up properly and responding fine and application for QUEUE as sender and MDB as receiver is executing fine. (See last line on server logs)
6)In JMSAdmin.config following properties are set up...
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
PROVIDER_URL=file:/C:/JNDI-Directory
7)JMSAdmin console shows following list... (as set up)

InitCtx/jms> display ctx

Contents of InitCtx/jms

.bindings java.io.File
a JMSExampleConnectionFactory com.ibm.mq.jms.MQConnectionFactory
a ExampleTopic com.ibm.mq.jms.MQTopic
a JMSExampleTopic com.ibm.mq.jms.MQTopic

4 Object(s)
0 Context(s)
4 Binding(s), 3 Administered

8)Is the way i am configuring the MQTopic and MQConnectionFactory is required via jmsadmin ?? I am not clear on this.plz. correct me.
9)So how to make sure that Topic as destination is physically available on Websphere MQ6.0 onto queue manager,
or is Topic logically present with q-manager. I am confused here, plz. throw some light here Topic to Qmanager relationship.

10)Below is the error message displayed onto the server console....

un(ThreadPool.java:1332)

[8/2/05 20:29:14:219 IST] 0000000e MDBListenerIm I WMSG0058I: Listener Port JMSExampleTopicPort will attempt to restart in 60 seconds
[8/2/05 20:29:14:234 IST] 00000016 WASLogger E CLASSNAME METHODNAME an internal error has occurred. Please contact your system administrator. Detail: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2019
[8/2/05 20:29:14:234 IST] 0000003e JMSExceptionL E WMSG0018E: Error on JMSConnection for MDB SubscriberDMDB , JMSDestination jms/JMSExampleTopic : javax.jms.JMSException: MQJMS2008: failed to open MQ queue


at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:553)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2546)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2747)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessage(MQBrokerSubscriptionEngine.java:2785)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.openDurableSubscription(MQBrokerSubscriptionEngine.java:888)

at com.ibm.mq.jms.MQMigrateSubscriptionEngine.openDurableSubscription(MQMigrateSubscriptionEngine.java:544)
at com.ibm.mq.jms.MQConnectionBrowser.pubSubSetup(MQConnectionBrowser.java:400)
at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:266)


at com.ibm.mq.jms.MQConnectionBrowser.<init>(MQConnectionBrowser.java:143)
at com.ibm.mq.jms.MQConnection.createDurableConnectionBrowser(MQConnection.java:3438)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:463)

at com.ibm.mq.jms.MQConnection.createDurableConnectionConsumer(MQConnection.java:3349)
at com.ibm.mq.jms.MQXAConnection.createDurableConnectionConsumer(MQXAConnection.java:328)
at com.ibm.ejs.jms.JMSConnectionHandle.createDurableConnectionConsumer(JMSConnectionHandle.java:1016)

at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:509)


at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:680)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:611)
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:971)
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)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:683)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:1678)
at com.ibm.ws.runtime.component.ComponentImpl$_AsynchInitializer.run(ComponentImpl.java:304)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)
---- Begin backtrace for Nested Throwables
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
at com.ibm.mq.MQQueue.putMsg2(MQQueue.java:1498)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2538)


at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2747)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessage(MQBrokerSubscriptionEngine.java:2785)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.openDurableSubscription(MQBrokerSubscriptionEngine.java:888)

at com.ibm.mq.jms.MQMigrateSubscriptionEngine.openDurableSubscription(MQMigrateSubscriptionEngine.java:544)
at com.ibm.mq.jms.MQConnectionBrowser.pubSubSetup(MQConnectionBrowser.java:400)
at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:266)


at com.ibm.mq.jms.MQConnectionBrowser.<init>(MQConnectionBrowser.java:143)
at com.ibm.mq.jms.MQConnection.createDurableConnectionBrowser(MQConnection.java:3438)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:463)

at com.ibm.mq.jms.MQConnection.createDurableConnectionConsumer(MQConnection.java:3349)
at com.ibm.mq.jms.MQXAConnection.createDurableConnectionConsumer(MQXAConnection.java:328)
at com.ibm.ejs.jms.JMSConnectionHandle.createDurableConnectionConsumer(JMSConnectionHandle.java:1016)

at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:509)


at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:680)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:611)
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:971)
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)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:683)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:1678)
at com.ibm.ws.runtime.component.ComponentImpl$_AsynchInitializer.run(ComponentImpl.java:304)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)

[8/2/05 20:29:14:391 IST] 0000003c MDBListenerIm E WMSG0059E: Maximum restart retry count of 5 reached for Listener Port JMSExampleTopicPort
[8/2/05 20:29:14:391 IST] 0000003a MDBListenerIm I WMSG0058I: Listener Port JMSExampleTopicPort will attempt to restart in 60 seconds
[8/2/05 20:29:14:438 IST] 00000016 MDBListenerIm W WMSG0019E: Unable to start MDB Listener SubscriberDMDB, JMSDestination jms/JMSExampleTopic : javax.jms.JMSException: MQJMS2008: failed to open MQ queue


at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:553)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2546)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2747)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessage(MQBrokerSubscriptionEngine.java:2785)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.openDurableSubscription(MQBrokerSubscriptionEngine.java:888)

at com.ibm.mq.jms.MQMigrateSubscriptionEngine.openDurableSubscription(MQMigrateSubscriptionEngine.java:544)
at com.ibm.mq.jms.MQConnectionBrowser.pubSubSetup(MQConnectionBrowser.java:400)
at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:266)


at com.ibm.mq.jms.MQConnectionBrowser.<init>(MQConnectionBrowser.java:143)
at com.ibm.mq.jms.MQConnection.createDurableConnectionBrowser(MQConnection.java:3438)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:463)

at com.ibm.mq.jms.MQConnection.createDurableConnectionConsumer(MQConnection.java:3349)
at com.ibm.mq.jms.MQXAConnection.createDurableConnectionConsumer(MQXAConnection.java:328)
at com.ibm.ejs.jms.JMSConnectionHandle.createDurableConnectionConsumer(JMSConnectionHandle.java:1016)

at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:509)


at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:680)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:611)
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:971)
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)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:683)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:1678)
at com.ibm.ws.runtime.component.ComponentImpl$_AsynchInitializer.run(ComponentImpl.java:304)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)
---- Begin backtrace for Nested Throwables
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
at com.ibm.mq.MQQueue.putMsg2(MQQueue.java:1498)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2538)


at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2747)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessage(MQBrokerSubscriptionEngine.java:2785)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.openDurableSubscription(MQBrokerSubscriptionEngine.java:888)

at com.ibm.mq.jms.MQMigrateSubscriptionEngine.openDurableSubscription(MQMigrateSubscriptionEngine.java:544)
at com.ibm.mq.jms.MQConnectionBrowser.pubSubSetup(MQConnectionBrowser.java:400)
at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:266)


at com.ibm.mq.jms.MQConnectionBrowser.<init>(MQConnectionBrowser.java:143)
at com.ibm.mq.jms.MQConnection.createDurableConnectionBrowser(MQConnection.java:3438)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:463)

at com.ibm.mq.jms.MQConnection.createDurableConnectionConsumer(MQConnection.java:3349)
at com.ibm.mq.jms.MQXAConnection.createDurableConnectionConsumer(MQXAConnection.java:328)
at com.ibm.ejs.jms.JMSConnectionHandle.createDurableConnectionConsumer(JMSConnectionHandle.java:1016)

at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:509)


at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:680)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:611)
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:971)
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)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:683)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:1678)
at com.ibm.ws.runtime.component.ComponentImpl$_AsynchInitializer.run(ComponentImpl.java:304)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)

[8/2/05 20:29:14:531 IST] 0000003e JMSExceptionL E WMSG0057E: Error on JMSConnection for MDB SubscriberDMDB , JMSDestination jms/JMSExampleTopic , JMS Linked Exception : com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
at com.ibm.mq.MQQueue.putMsg2(MQQueue.java:1498)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2538)


at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessageInternal(MQBrokerSubscriptionEngine.java:2747)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.sendBrokerMessage(MQBrokerSubscriptionEngine.java:2785)
at com.ibm.mq.jms.MQBrokerSubscriptionEngine.openDurableSubscription(MQBrokerSubscriptionEngine.java:888)

at com.ibm.mq.jms.MQMigrateSubscriptionEngine.openDurableSubscription(MQMigrateSubscriptionEngine.java:544)
at com.ibm.mq.jms.MQConnectionBrowser.pubSubSetup(MQConnectionBrowser.java:400)
at com.ibm.mq.jms.MQConnectionBrowser.MQConnectionBrowserInit(MQConnectionBrowser.java:266)


at com.ibm.mq.jms.MQConnectionBrowser.<init>(MQConnectionBrowser.java:143)
at com.ibm.mq.jms.MQConnection.createDurableConnectionBrowser(MQConnection.java:3438)
at com.ibm.mq.jms.MQConnectionConsumer.<init>(MQConnectionConsumer.java:463)

at com.ibm.mq.jms.MQConnection.createDurableConnectionConsumer(MQConnection.java:3349)
at com.ibm.mq.jms.MQXAConnection.createDurableConnectionConsumer(MQXAConnection.java:328)
at com.ibm.ejs.jms.JMSConnectionHandle.createDurableConnectionConsumer(JMSConnectionHandle.java:1016)

at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:509)


at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:680)
at com.ibm.ejs.jms.listener.MDBListenerImpl.start(MDBListenerImpl.java:611)
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:971)
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)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:683)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:1678)
at com.ibm.ws.runtime.component.ComponentImpl$_AsynchInitializer.run(ComponentImpl.java:304)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1332)

[8/2/05 20:29:14:562 IST] 00000016 MDBListenerIm I WMSG0058I: Listener Port JMSExampleTopicPort will attempt to restart in 60 seconds
[8/2/05 20:29:14:641 IST] 0000003e MDBListenerIm I WMSG0058I: Listener Port JMSExampleTopicPort will attempt to restart in 60 seconds
[8/2/05 20:29:14:641 IST] 00000016 MsgListenerPo W WMSG0049E: Failed to start MDB SubscriberDMDB against listener port JMSExampleTopicPort
[8/2/05 20:29:14:766 IST] 00000016 ApplicationMg A WSVR0221I: Application started: JMSExample
[8/2/05 20:29:14:859 IST] 0000000a TCPChannel A TCPC0001I: TCP Channel TCP_1 is listening on host * (IPv4) port 9060.
[8/2/05 20:29:14:984 IST] 0000000a WSChannelFram A CHFW0019I: The Transport Channel Service has started chain WCInboundAdmin.
[8/2/05 20:29:15:047 IST] 0000000a TCPChannel A TCPC0001I: TCP Channel TCP_2 is listening on host * (IPv4) port 9080.
[8/2/05 20:29:15:047 IST] 0000000a WSChannelFram A CHFW0019I: The Transport Channel Service has started chain WCInboundDefault.
[8/2/05 20:29:15:062 IST] 0000000a TCPChannel A TCPC0001I: TCP Channel TCP_3 is listening on host * (IPv4) port 9043.
[8/2/05 20:29:15:062 IST] 0000000a WSChannelFram A CHFW0019I: The Transport Channel Service has started chain WCInboundAdminSecure.
[8/2/05 20:29:15:141 IST] 0000000a TCPChannel A TCPC0001I: TCP Channel TCP_4 is listening on host * (IPv4) port 9443.
[8/2/05 20:29:15:250 IST] 0000000a WSChannelFram A CHFW0019I: The Transport Channel Service has started chain WCInboundDefaultSecure.
[8/2/05 20:29:15:312 IST] 0000000a WSChannelFram A CHFW0019I: The Transport Channel Service has started chain SOAPAcceptorChain1.
[8/2/05 20:29:15:328 IST] 0000000a WSChannelFram A CHFW0019I: The Transport Channel Service has started chain SOAPAcceptorChain2.
[8/2/05 20:29:15:328 IST] 0000000a WSChannelFram A CHFW0019I: The Transport Channel Service has started chain SOAPAcceptorChain3.
[8/2/05 20:29:15:359 IST] 0000000a WSChannelFram A CHFW0019I: The Transport Channel Service has started chain SOAPAcceptorChain4.
[8/2/05 20:29:15:375 IST] 00000016 SchedulerServ I SCHD0077I: The Scheduler Service is starting the Schedulers.
[8/2/05 20:29:15:375 IST] 00000016 SchedulerServ I SCHD0078I: The Scheduler Service has completed starting the Schedulers.
[8/2/05 20:29:15:391 IST] 0000000a RMIConnectorC A ADMC0026I: The RMI Connector is available at port 2809
[8/2/05 20:29:15:453 IST] 0000003f WorkSpaceMana A WKSP0023I: Workspace configuration consistency check is enabled.
[8/2/05 20:29:16:234 IST] 0000000a WsServerImpl A WSVR0001I: Server server1 open for e-business
[8/2/05 20:29:20:000 IST] 00000048 ServletWrappe A SRVE0242I: [transfer]: Initialization successful.
[8/2/05 20:29:20:125 IST] 00000032 WorkSpaceMana A WKSP0023I: Workspace configuration consistency check is enabled.
[8/2/05 20:29:20:141 IST] 00000048 WorkSpaceMana A WKSP0023I: Workspace configuration consistency check is enabled.
[8/2/05 20:29:27:844 IST] 00000049 WorkSpaceMana A WKSP0023I: Workspace configuration consistency check is enabled.
[8/2/05 20:36:25:812 IST] 00000053 SystemOut O MESSAGE DRIVEN BEAN 'Receiver' CONSUMED MESSAGE: message from queue which i configured......... :-)

mch...@australianunity.com.au

no leída,
2 jul 2006, 20:52:212/7/06
a
I have a similar problem. I'm using WMQ 6.0 WAS 6.0 JMS Point to Point queues. Listner port just will not start without giving me any reasons in the logs. Can anyone help?
[3/07/06 10:38:06:258 EST] 0000002a ApplicationMg A WSVR0200I: Starting application: EAR_Koukia_Proxy
[3/07/06 10:38:06:305 EST] 0000002a EJBContainerI I WSVR0207I: Preparing to start EJB jar: KoukiaProxy.jar
[3/07/06 10:38:06:305 EST] 0000002a EJBContainerI I WSVR0037I: Starting EJB jar: KoukiaProxy.jar
[3/07/06 10:38:06:352 EST] 0000002a MDBListenerIm I WMSG0058I: Listener Port HUB_TO_KOUKIA will attempt to restart in 60 seconds
[3/07/06 10:38:06:367 EST] 0000002a ApplicationMg E WSVR0101W: An error occurred starting, EAR_Koukia_Proxy
[3/07/06 10:38:06:367 EST] 0000002a ApplicationMg A WSVR0217I: Stopping application: EAR_Koukia_Proxy
[3/07/06 10:38:06:383 EST] 0000002a EJBContainerI I WSVR0041I: Stopping EJB jar: KoukiaProxy.jar
[3/07/06 10:38:06:383 EST] 0000002a ApplicationMg A WSVR0220I: Application stopped: EAR_Koukia_Proxy
[3/07/06 10:38:06:977 EST] 00000030 ServletWrappe A SRVE0242I: [/secure/javascriptToSession.jsp]: Initialization successful.
[3/07/06 10:40:54:820 EST] 0000002b ApplicationMg A WSVR0200I: Starting application: EAR_Koukia_Proxy
[3/07/06 10:40:54:836 EST] 0000002b EJBContainerI I WSVR0207I: Preparing to start EJB jar: KoukiaProxy.jar
[3/07/06 10:40:54:852 EST] 0000002b EJBContainerI I WSVR0037I: Starting EJB jar: KoukiaProxy.jar
[3/07/06 10:40:54:883 EST] 0000002b ApplicationMg A WSVR0221I: Application started: EAR_Koukia_Proxy
[3/07/06 10:41:39:664 EST] 00000030 MDBListenerIm I WMSG0058I: Listener Port HUB_TO_KOUKIA will attempt to restart in 60 seconds
[3/07/06 10:42:39:664 EST] 0000000f MDBListenerIm I WMSG0058I: Listener Port HUB_TO_KOUKIA will attempt to restart in 60 seconds
[3/07/06 10:43:39:664 EST] 0000000e MDBListenerIm I WMSG0058I: Listener Port HUB_TO_KOUKIA will attempt to restart in 60 seconds
[3/07/06 10:44:39:664 EST] 00000027 MDBListenerIm I WMSG0058I: Listener Port HUB_TO_KOUKIA will attempt to restart in 60 seconds
[3/07/06 10:45:39:727 EST] 0000000f MDBListenerIm I WMSG0058I: Listener Port HUB_TO_KOUKIA will attempt to restart in 60 seconds
[3/07/06 10:46:39:727 EST] 0000000f MDBListenerIm E WMSG0059E: Maximum restart retry count of 5 reached for Listener Port HUB_TO_KOUKIA

Stephen Cocks

no leída,
3 jul 2006, 8:53:443/7/06
a
WAS 6.0 ships with a version of the WMQ 5.3 Java Client JARS. This normally
allows the WMQ Messaging Provider support to work, but it is also possible
to point WAS at a more recent client library (obviously necessary to exploit
any new provider functionality). To do this set the MQ_INSTALL_ROOT
environment variable (WebSphere Variables) to the directory where WebSphere
MQ is installed. IBM WebSphere Application Server uses the MQ_INSTALL_ROOT
to locate the WebSphere MQ libraries for the WebSphere MQ Provider. Save and
restart the server.

Exactly which versions of WAS and WMQ are you using - i.e. refresh packs/
fix packs/ iFixes etc?
--
Stephen Cocks
WESB/WPS System Administration

<mch...@australianunity.com.au> wrote in message
news:127960189.1151887976...@ltsgwas009.sby.ibm.com...

mch...@australianunity.com.au

no leída,
3 jul 2006, 19:56:533/7/06
a
Stephen you are an absolute legend!! The listener port started successfully after I have pointed the MQ_INSTALL_ROOT environment variable to where I installed Websphere MQ 6.0 (C:\Program Files\IBM\WebSphere MQ\). I'm guessing the 2 mq jars that comes with WAS 6.0 is buggy.

Versions I'm using are as follows:

IBM WebSphere Application Server, 6.0.0.1
Build Number: o0445.08
Build Date: 11/10/04

IBM Websphere MQ 6.0 (with no fixpacks etc)

I was basically trying to migrate my app from WAS 5.1 WMQ 5.3 using the same application EAR that as exported from WSAD 5. I basically configured WAS 6.0 the same way as WAS 5 using the Websphere MQ JMS provider and listener ports.

What I found really frustrating was that when the listener port did not start, there were no errors in the systemout.log or the trace.log to indicate what has gone wrong. To add to this the administrative console is very misleading when it indicates that the listener port has started successfully when in fact it hasn't!

Thanks for your help again Stephen

prko...@yahoo.com

no leída,
11 abr 2007, 1:34:3011/4/07
a
I am still facing the same problem. Iam RAD 6 and MQ 6

RAD:
Version: 6.0.0
Build id: 20041117_2230

MQ 6.0.0

I have added the system environment variable MQ_INSTALL_ROOT as D:\Program Files\IBM\WebSphere MQ.

see the log filr below.
log:

[4/10/07 22:29:29:594 GMT-07:00] 00000015 MDBListenerIm I WMSG0058I: Listener Port JMSExampleTopicPort will attempt to restart in 60 seconds
[4/10/07 22:29:29:688 GMT-07:00] 00000015 ApplicationMg E WSVR0101W: An error occurred starting, JMSExample
[4/10/07 22:29:29:984 GMT-07:00] 00000015 ApplicationMg A WSVR0217I: Stopping application: JMSExample
[4/10/07 22:29:30:109 GMT-07:00] 00000015 EJBContainerI I WSVR0041I: Stopping EJB jar: JMSExampleEJB.jar
[4/10/07 22:29:30:469 GMT-07:00] 00000015 ApplicationMg A WSVR0220I: Application stopped: JMSExample


Please help.

Regards,
Prasanna

Ken Hygh

no leída,
11 abr 2007, 7:32:1111/4/07
a

Not enough detail here, there's probably more in the log about unable to
connect to port.

Most likely reason is that you have another process bound to that port.

Ken

Graham Hopkins

no leída,
11 abr 2007, 7:45:3011/4/07
a
<prko...@yahoo.com> wrote in message
news:1098519739.117626977...@ltsgwas009.sby.ibm.com...

There should be some more information further up the log saying why the LP
isnt starting and maybe some information in the WebSphere MQ queue managers
logs, some of the common problems you may hit are :

The host/port are wrong on the CF so you fail to connect,
The WebSphere MQ listener/queue manager isnt running so you fail to connect
You specified bindings for the connection type when the want to connect to a
remote queue manager so you fail to connect
The Broker isnt running so it times out waiting for a broker response
You specified the wrong version for the broker on the connection factory
(i.e.specified basic instead of advanced) so it either times out or gets an
unexpected response from the broker

Regards

Graham


0 mensajes nuevos