Author |
Message
|
ChrisW |
Posted: Wed May 25, 2005 8:27 am Post subject: Heartbeats when sender channel inactive? |
|
|
Voyager
Joined: 20 May 2001 Posts: 78 Location: UK
|
I have searched all manuals and this site but I cannot find the answer to this question - Do heartbeats (HBINT) happen when a sender channel is in an INACTIVE state?
Basically we want to find out as soon as possible when there is a problem with the network. I intend ensuring TCP KeepAlive but I gather that MQ level heartbeats will also be useful. However, do they happen if the channel is inactive?
Thanks,
Chris. |
|
Back to top |
|
 |
vennela |
Posted: Wed May 25, 2005 8:37 am Post subject: Re: Heartbeats when sender channel inactive? |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
ChrisW wrote: |
Do heartbeats (HBINT) happen when a sender channel is in an INACTIVE state?
|
I don't think so |
|
Back to top |
|
 |
ChrisW |
Posted: Wed May 25, 2005 8:40 am Post subject: |
|
|
Voyager
Joined: 20 May 2001 Posts: 78 Location: UK
|
I think that makes most sense. This is I suppose the reason why HBINT should be less than DISCINT? |
|
Back to top |
|
 |
ChrisW |
Posted: Wed May 25, 2005 8:57 am Post subject: |
|
|
Voyager
Joined: 20 May 2001 Posts: 78 Location: UK
|
So......
If messages are flowing and the network goes down then the channel goes into RETRY.
If no message has gone across since HBINT then a heartbeat is sent and we will know if the network has gone down.
The next question is:
If the channel is INACTIVE (and so nothing is being sent) then TCP KeepAlive will know if the network goes down. However, will it tell MQ? Or will it just make it more likely that when the channel starts it will do so successfully?
Its starting to look like DISCINT(0) may be an option but this is something I don't like doing. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed May 25, 2005 9:00 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Why not just monitor the network directly? _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
ChrisW |
Posted: Wed May 25, 2005 9:04 am Post subject: |
|
|
Voyager
Joined: 20 May 2001 Posts: 78 Location: UK
|
Couple of problems here -
1. Team responsibilities within this company and getting work done!
2. Communication is between companies over VPN. The "network problem" could be on either side but we still want to know so we can alert the other party that there is a problem and hopefully we can both look. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Wed May 25, 2005 1:54 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
ChrisW wrote: |
If the channel is INACTIVE (and so nothing is being sent) then TCP KeepAlive will know if the network goes down. However, will it tell MQ? Or will it just make it more likely that when the channel starts it will do so successfully?
Its starting to look like DISCINT(0) may be an option but this is something I don't like doing. |
Yeah, Keep Alive will tell MQ that the other side is gone, but if the channel is INACTIVE, there is no other side - a benifit to an INACTIVE channel. While the channel is INACTIVE, let Edward Scissorhands go nuts on your network cables. If it is all fixed before the channel need to start up, you will never know anything was wrong. The very reason you do NOT want DISCINT set to 0, unless you have a compelling reason to do so. The only reason I acan think of is your messages are so time sensitive, and so infrequently sent, that they cannot afford the delay a triggering channel imposes (usually only about a second, if that). _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
PeteHanbury |
Posted: Mon Jul 11, 2005 6:53 am Post subject: AdoptNewMCA |
|
|
 Novice
Joined: 13 Apr 2004 Posts: 23 Location: US AND EUROPE
|
Chris look,
Heartbeats and disctinct intervals and that crappy 'keepalive ' option (That never worked anyway) have really been superceeded by what is known as AdoptNewMCA
It just involves setting a couple of flags and is very easy to do. Using this means of keeping your channels going will solve the problems you are having with 'RETRY STATE' i used ity myself at IBM France a couple of yearsd ago to solve the problems you describe.
Give us a bell if you need more help 07854011590
Regards
Pete _________________ PeteHanbury
Independent IBM MQSeries/MQSI Architecture Certified Contractor |
|
Back to top |
|
 |
PeterPotkay |
Posted: Mon Jul 11, 2005 7:00 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Keep Alive and HBs still are very useful for SVRCONN channels, where AdoptMCA does not apply.
But for all other channels, yes, AdoptMCA really is a good idea and you should definitly use it. If you have particualry long DISCINT, then HBs are still recomended, even if you have AdoptMCA. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
PeteHanbury |
Posted: Mon Jul 11, 2005 7:23 am Post subject: CHANNELS |
|
|
 Novice
Joined: 13 Apr 2004 Posts: 23 Location: US AND EUROPE
|
Chris you may also want to look at having your channels 'triggered to start when messages arrive. (Although that is probably getting away from the subject of your origional post) _________________ PeteHanbury
Independent IBM MQSeries/MQSI Architecture Certified Contractor |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Jul 11, 2005 7:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Chris hasn't been reading this thread for probably a month now. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
|