| Author |
Message
|
| andy1382 |
 Posted: Mon Apr 12, 2010 11:02 am Post subject: Send Email when MQ listener is unable to connect to MQ Queue |
 |
|
Newbie
Joined: 12 Apr 2010
Posts: 3
|
Hi All,
I am using Websphere application server 6.1 and I have MDB and Listener port for this MDB. I have remote MQ queue which is defined in WAS. Now in case where MDB and listerner are started and MQ queue is going down, Is there any way to send Email or Notification like MQ listener is unable to connect to MQ Quque or MQ manager is down..?
Because I think in MDB its not possible to find out if MQ queue is down or listener is unable to connect or start.
Please advice me on this.
Thanks,
AD. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Apr 12, 2010 1:49 pm Post subject: Re: Send Email when MQ listener is unable to connect to MQ Q |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| andy1382 wrote: |
| Because I think in MDB its not possible to find out if MQ queue is down or listener is unable to connect or start. |
Technically queues don't go down, queue managers do but in the event that there's a problem with your MDB unable to connect (for any reason) then you'd get a reason code & this would be handled as normal.
If you're trying to find out if the remote queue you're sending to is unavailable then a) you're right you can't determine that, b) it's none of your business because if you've successfully put a message you can be assured it will reach the queue & c) there's no need to email or notify anyone because the infrastructure monitoring will have already done it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| andy1382 |
| Posted: Tue Apr 13, 2010 6:48 am Post subject: |
|
|
Newbie
Joined: 12 Apr 2010
Posts: 3
|
Thanks Vitor,
Last thing I want to clarify is this. Lets say Queue and Queue Manager all are running fine and because of network issue Queue Listener is unable to read queue (assume this happend one morning and day b4 all were working fine). Please confirm that in this case there is no way that Listener or MDB can know or send information to infrastructure that they are not able to read queue as infrastructure point of view all are running fine.
Thank you again. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 13, 2010 7:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Ok, let's define some terms and guidelines here. Firstly queues don't run, queue managers run. Secondly, a "listener" is something quite specific in WMQ terms and not what I think you're talking about here. Thirdly, in any problem situation it's always the case it was working fine the day before. 
So assuming that by "queue listener" you mean an MDB or other app that's listening for messages on a queue. If that can't connect to a WMQ object for any reason it will receive a reason code, probably a fairly generic one. That you could email, or in some other way notify someone.
Now we extend this to the remote queue you mention in the original post. Your MDB has no way to tell if the WMQ object which that resolves to (or the queue manager which hosts it) is up, down, on fire or abducted by aliens. Your part of the operation is working just fine and it will all be good.
The reason you don't need to know anything about the remote set up is because that is the province of the WMQ administrator. It's for him to determine all this is working even if they don't administer the remote part directly; they'll still be able to determine that something's wrong. One of the key planks of the WMQ platform is it's ability to allow applications to keep sending messages in the face of fairly serious problems & for those messages to arrive eventually.
Hope that helps.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| andy1382 |
| Posted: Tue Apr 13, 2010 7:32 am Post subject: |
|
|
Newbie
Joined: 12 Apr 2010
Posts: 3
|
Got it. At the end of the day its none of my business.. 
Thank You. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 13, 2010 7:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| andy1382 wrote: |
| Got it. At the end of the day its none of my business.. |
It's why your site paid IBM big $$$ for the software, and your WMQ admin earns $$$. To ensure it's none of your business and you can live your life free from this kind of care.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Apr 13, 2010 8:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Now to put a slight spin on this.
WebSphere Application Server may not pass an issue with the MDB Listener into your MDB code.
It may decide to do it's job and report that error to the WAS Administrator. Who presumably also makes $$$ and may possible have another hat next to her desk that says "MQ Administrator" (and wishes she could get paid once for each hat).
And presumably the WAS Administrator has things configured such that, should WAS report such an issue, then they will get paged.
So it's also not really your problem. But it's at least closer. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 13, 2010 9:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| So it's also not really your problem. But it's at least closer. |
But not so close as to influence the happy, carefree life of an MDB in any design sense. Though the wailing & contact admin of teeth as the various administrators (if they're not indeed the same person) as they work through the problem might be unsettleing
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
