| Author |
Message
|
| kavithadhevi |
 Posted: Fri Aug 23, 2002 9:46 am Post subject: HEARTBEAT INTERVAL |
 |
|
Master
Joined: 14 May 2002
Posts: 201
Location: USA
|
Hi,
Based on the discussion about HEARTBEAT Vs ADOPT MCA, I would like to post about my systems and my doubts. I appreciate if you could explain me.
We have a tandem system running mq5.1 connecting to a NT server running mq 5.2.
In our scenario we see the sender channel in a running state on the Tandem, and the NT receiver channels is inactive. The problem is the Tandem sender channel never goes into a retry state. We have to stop/start the tandem sender channel. How can we get this to work correctly?
We have the disconnect interval set to 0 since the channel is in use 7x24. We see a TCP/IP MQ error on the NT server but the Tandem thinks
everything is fine. What setting can be used to better correct this problem?
_________________
Thanks in Advance. 
Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Aug 23, 2002 12:29 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
If you feel your channel is in use 24/7 then set the DISCINT to an hour (which means it disconnects after an hour of inactivity). At DISCINT 0 the channel always goes to the retry state. Have you tried the short retry interval and long retry interval and their corresponding counts.
My gut feeling is: Having your DISCINT 0 and if you have the retry counts fairly short then the sender may stop retrying after the counts are exhausted
--
Venny |
|
| Back to top |
|
|
| jc_squire |
| Posted: Sun Aug 25, 2002 4:01 pm Post subject: |
|
|
Centurion
Joined: 14 Apr 2002
Posts: 105
Location: New Zealand
|
Well, you will be pleased to know that you are not the only one who has seen this.
As far as I know this is a known problem with 5.1 - no TCP/IP time out. This has been resolved in 5.2
Essentially the tcp/ip time out (twice that of HBINT) checks if the connection is still active and if not it resets the connection.
The only solution that I am aware of is to upgrade to 5.2
Regards
_________________
J C Squire
IBM Certified Specialist - MQSeries |
|
| Back to top |
|
|
| mrlinux |
| Posted: Wed Sep 04, 2002 10:33 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
When the sender channel is in the run state is there any messages in its
xmitq, if not try sending test message this throw it into retry.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| kavithadhevi |
| Posted: Thu Sep 05, 2002 12:15 pm Post subject: |
|
|
Master
Joined: 14 May 2002
Posts: 201
Location: USA
|
Thank you all , and Jeff thats a good suggestion, i'll test that and post my result.
_________________
Thanks in Advance.
Kavitha
IBM Certified System Administrator
Websphere MQ v 5.3
www.zealphoenix.com |
|
| Back to top |
|
|
|
|
