File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes EJB and other Java EE Technologies and the fly likes MDB not connecting to JMS (MQ) .... Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "MDB not connecting to JMS (MQ) ...." Watch "MDB not connecting to JMS (MQ) ...." New topic
Author

MDB not connecting to JMS (MQ) ....

Ganesh Gore
Greenhorn

Joined: Jan 03, 2011
Posts: 24

Hello,

Please find the error log below....


<Sep 2, 2013 2:45:13 PM GMT+05:30> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: EventQueueListener is unable to connect to the JMS destination or bind to JCA resource adapter: jms/FCBSchedularRequestQ. Connection failed after 2 attempts. The MDB will attempt to reconnect/rebind every 1 seconds. This log message will repeat every 600 seconds until the condition clears.>
<Sep 2, 2013 2:45:13 PM GMT+05:30> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: EventQueueListener is unable to connect to the JMS destination: jms/FCBSchedularRequestQ. The Error was:
[EJB:011014]The Message-Driven EJB failed while creating a JMS Connection. The error was:
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '10.180.183.208:FCBSchedularQM'
Linked exception: com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
Nested exception: com.ibm.mqservices.MQInternalException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009.
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '10.180.183.208:FCBSchedularQM'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:586)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2110)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1532)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:150)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:185)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:112)
at weblogic.ejb.container.internal.JMSConnectionPoller.getConnection(JMSConnectionPoller.java:487)
at weblogic.ejb.container.internal.JMSConnectionPoller.createJMSConnection(JMSConnectionPoller.java:1991)
at weblogic.ejb.container.internal.JMSConnectionPoller.connect(JMSConnectionPoller.java:826)
at weblogic.ejb.container.internal.MDConnectionManager.timerExpired(MDConnectionManager.java:170)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
NestedException Message is :MQJMS2005: failed to create MQQueueManager for '10.180.183.208:FCBSchedularQM'>


Ganesh Gore
Greenhorn

Joined: Jan 03, 2011
Posts: 24

<?xml version="1.0" encoding="UTF-8"?>
<!--
** This file was automatically generated by
** EJBGen WebLogic Server 10.0 SP0 Wed May 9 18:10:27 EDT 2007 933139
-->
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>EventQueueListener</ejb-name>
<message-driven-descriptor>
<pool>
<initial-beans-in-free-pool>2</initial-beans-in-free-pool>
<max-beans-in-free-pool>10</max-beans-in-free-pool>
</pool>
<destination-jndi-name>jms/FCBSchedularRequestQ</destination-jndi-name>
<connection-factory-jndi-name>
jms/FCBSchedularQM
</connection-factory-jndi-name>
<jms-polling-interval-seconds>
1
</jms-polling-interval-seconds>
</message-driven-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>10</trans-timeout-seconds>
</transaction-descriptor>
<dispatch-policy>FCRJGefuSchedulerNHWM</dispatch-policy>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>



<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar id="ejb-jar_ID">
<display-name>FCRJGefuSchedulerNH</display-name>
<enterprise-beans>
<message-driven>
<ejb-name>EventQueueListener</ejb-name>
<ejb-class>com.iflex.fcr.nh.xface.EventQueueListener</ejb-class>
<transaction-type>Bean</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
</ejb-jar>
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: MDB not connecting to JMS (MQ) ....