| Author |
Message
|
| siva.kasetty |
 Posted: Tue Dec 08, 2009 12:11 am Post subject: Unable to start MDB Listener |
 |
|
Apprentice
Joined: 17 Mar 2008
Posts: 45
|
Hi,
I am using MQ export binding for polling a MQ queue.
Binding create a listener in Admin console when application deployed to server.
I am testing a failure case that I want MDB Listener up and running when MQ down means Queue manager is down.
But its not happening.
MDB Listener goes stopped state after 5 retries.
giving following exp:
WMSG0019E: Unable to start MDB Listener _export.Component1Export1MQ, JMSDestination TESTMQ/Component1Export1_MQ_RECEIVE_D : javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'localhost:TEST'
so how to keep MDB Listener Stared state always.
Thanks... |
|
| Back to top |
|
 |
| moonwalker |
| Posted: Mon Jan 25, 2010 2:39 am Post subject: |
|
|
Apprentice
Joined: 02 Jun 2009
Posts: 42
|
Well this according to me is not possible because a listener always listens to a queue accessible through a port of the Queue Manager.
If there is an incoming request on that queue then the listener invokes the MDB.
Once the Queue manager goes down then the port of the queue manager also gets closed and the listener would be unable to access the queue and hence the error. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 25, 2010 6:10 am Post subject: Re: Unable to start MDB Listener |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| siva.kasetty wrote: |
| I am testing a failure case that I want MDB Listener up and running when MQ down means Queue manager is down. |
What exactly would it be listening to? 
Surely it makes more sense to restart it when the queue manager comes back up? Or reconnect via client to another, still running MQ if your design supports that?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| wooda |
| Posted: Tue Mar 09, 2010 3:11 am Post subject: |
|
|
Master
Joined: 21 Nov 2003
Posts: 265
Location: UK
|
As I suspect you know the error javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'localhost:TEST'
means that a connection could not be made to the QMGR defined in the CF.
There should be the MQ specific error in the stack somewhere as well.
How to keep a connectipn up ? Well you'll need to connect to another QMGr as the down one obviously cannot be connected to....
You might consider using CCDT in the CF to provide a list of possible QMGRs to connect to ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Mar 09, 2010 12:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| wooda wrote: |
As I suspect you know the error javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'localhost:TEST'
means that a connection could not be made to the QMGR defined in the CF.
There should be the MQ specific error in the stack somewhere as well.
How to keep a connectipn up ? Well you'll need to connect to another QMGr as the down one obviously cannot be connected to....
You might consider using CCDT in the CF to provide a list of possible QMGRs to connect to ? |
Obviously a CCDT is not always advisable, especially not when the MDB is expected to process inbound messages...that will go to the indicated destination. If you do load balancing in a cluster, you should have an MDB listening to each possible destination.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
