Joined: 09 Jan 2005 Posts: 41 Location: Queens, NY
My application never re-started the channel itself; it always just notified so the administrators of the network could investigate and/or re-start, using WebSphere MQ Explorer or a similar application. _________________ Chaim Mattis Keller
Shadow Financial Services Corp
ckeller@shadowfinancial.com
Of course the final decision is yours but .... I would definately recommend triggered channels and a monitoring system built independently of the application.
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
cmkeller wrote:
My application never re-started the channel itself; it always just notified so the administrators of the network could investigate and/or re-start, using WebSphere MQ Explorer or a similar application.
So you've re-invented the monitoring function already implemented by every software package that can monitor MQ, with the added twist you're not allowing MQ to attempt resolution itself? Your solution would be "acceptable" if the MQ channels were configured never to go inactive but in this situation you're reinventing a lot of wheels while making a rod for your own back.
You implement triggered channels, I'll try unmixing my metaphores. _________________ Honesty is the best policy.
Insanity is the best defence.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum