| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Disconnect Interval |
« View previous topic :: View next topic » |
| Author |
Message
|
| mvic |
 Posted: Tue Jan 26, 2010 4:58 pm Post subject: |
 |
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| PeterPotkay wrote: |
| J.D wrote: |
| It is Cluster-Receiver Channel. |
Um, you could have hundreds or thousands of channel instances of the same name when cluster receivers are concerned, all starting and stopping at various times. It each instance keeps track of its own DISCINT. |
Excellent point.
However check out the "Process(9045.983)" in one of JD's followup posts; this is a sure sign that it's the same channel instance as other occurrences having the same identifier. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Jan 26, 2010 5:13 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9482
Location: US: west coast, almost. Otherwise, enroute.
|
mvic says:
| Quote: |
| Still, I think that DISCINT is an attribute you can give to both a CLUSSDR and a CLUSRCVR. Could it be that the 6000 is being negotiated down to a lower value that is held in the partner definition? |
Ooooh, I like it.
From Mr. WMQ Intercommunications:
This is a time-out attribute, specified in seconds, for the server, cluster-sender, sender, and cluster-receiver channels.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| J.D |
| Posted: Tue Jan 26, 2010 5:30 pm Post subject: |
|
|
Voyager
Joined: 18 Dec 2009
Posts: 92
Location: United States
|
| We have only 5 Queue Manager's in this Cluster and all the Cluster-sender and Cluster-Receiver Channels have DISCINT(6000). |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 26, 2010 7:32 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9482
Location: US: west coast, almost. Otherwise, enroute.
|
From the Intercommunications manual:
| Quote: |
Disconnect interval (DISCINT)
The disconnect interval is the length of time after which a channel will close down if no message arrives on the transmission queue during that period.
This is a time-out attribute, specified in seconds, for the server, cluster-sender, sender, and cluster-receiver channels. The interval is measured from the point at which a batch ends, that is when the batch size is reached or when the batch interval expires and the transmission queue becomes empty. If no messages arrive on the transmission queue during the specified time interval, the channel closes down. (The time is approximate.) |
I can imagine that time is approximate anticipates a 10-minute discrepancy...
Perhaps someone from the WMQ factory can offer some insight.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mvic |
| Posted: Wed Jan 27, 2010 1:41 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| bruce2359 wrote: |
| I can imagine that time is approximate anticipates a 10-minute discrepancy... |
But the OP saw the channel end after approx 30 minutes, which is a long way short of the 100 they were expecting.
A PMR is the only way forward at this point, IMHO. |
|
| Back to top |
|
|
| J.D |
| Posted: Wed Jan 27, 2010 11:21 am Post subject: |
|
|
Voyager
Joined: 18 Dec 2009
Posts: 92
Location: United States
|
| The HBINT is set to 300 and DISCINT set to 6000 on our channels. So when there are no messages on XMITQ, the sending MCA will send heart beat flow to the receiving MCA, thus giving the receiving MCA to Quiesce the channel without waiting for the disconnect interval to expire. My assumption is receiving channel goes to inactive when there are no messages flows b/w the sender and receiver qmgr's in 300 seconds interval. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 27, 2010 12:57 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
| J.D wrote: |
| The HBINT is set to 300 and DISCINT set to 6000 on our channels. So when there are no messages on XMITQ, the sending MCA will send heart beat flow to the receiving MCA, thus giving the receiving MCA to Quiesce the channel without waiting for the disconnect interval to expire. My assumption is receiving channel goes to inactive when there are no messages flows b/w the sender and receiver qmgr's in 300 seconds interval. |
That is not how Heartbeats work. Heartbeats will never cause a running channel to end.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
