| Author |
Message
|
| J.D |
 Posted: Tue Jan 26, 2010 2:27 pm Post subject: Disconnect Interval |
 |
|
Voyager
Joined: 18 Dec 2009
Posts: 92
Location: United States
|
| The disconnect interval in our cluster channels is been set to 6000 which is default i guess. My question is it 6000 sec or ms or 1/10 sec? In the manual it said, we can set the interval in seconds. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jan 26, 2010 2:49 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
If the manual says seconds, why do you think it might be a different unit?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 26, 2010 2:54 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
What value do you see in setting disconnect interval in 1/10ths of seconds vs. seconds?
_________________
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 2:56 pm Post subject: |
|
|
Voyager
Joined: 18 Dec 2009
Posts: 92
Location: United States
|
If it is seconds then channel should go to inactive state after waiting for 6000 sec i.e 100 minutes. But when i checked the logs, channel going to inactive before the disconnect interval expires.
Error Logs:
01/25/10 04:56:48 AM - Process(9045.983) User(mqm) Program(amqrmppa)
AMQ9002: Channel 'TO.XXXX' is starting.
EXPLANATION:
Channel 'TO.XXXX' is starting.
ACTION:
None.
-------------------------------------------------------------------------------
01/25/10 05:28:12 AM - Process(9045.983) User(mqm) Program(amqrmppa)
AMQ9545: Disconnect interval expired.
EXPLANATION:
Channel 'TO.XXXX' closed because no messages arrived on the transmission queue within the disconnect interval period.
ACTION:
None. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 26, 2010 2:58 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Well that is interesting. If that's a supported version of WMQ I'd raise a PMR, including that log snippet and the channel definitions in question.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 26, 2010 3:10 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
Have you changed the disconnect interval?
_________________
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 3:30 pm Post subject: |
|
|
Voyager
Joined: 18 Dec 2009
Posts: 92
Location: United States
|
We didn't changed and it's the default value. All our Test and Prod channels has the same default value i.e 6000.
Version Info:
WMQ 6.0.2.2
Solaris 10 |
|
| Back to top |
|
|
| mvic |
| Posted: Tue Jan 26, 2010 3:39 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| J.D wrote: |
| If it is seconds then channel should go to inactive state after waiting for 6000 sec i.e 100 minutes. |
When your channel is running, please can you post output from this command in runmqsc:
| Code: |
| dis chs(YOURCHANNELNAME) hbint |
|
|
| Back to top |
|
|
| J.D |
| Posted: Tue Jan 26, 2010 3:54 pm Post subject: |
|
|
Voyager
Joined: 18 Dec 2009
Posts: 92
Location: United States
|
|
| Back to top |
|
|
| mvic |
| Posted: Tue Jan 26, 2010 4:04 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
What are the HBINT settings on the two channel definitions (SDR/RCVR) etc.?
Well we know it is 6000 on one end. What is it on the other end? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Jan 26, 2010 4:44 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
mvic, you are asking about HBINT and not DISCINT? I don't know of any value in HBINT on either end of the channel pair that would cause a channel to end with a message in the log saying "AMQ9545: Disconnect interval expired."
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Jan 26, 2010 4:46 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
J.D., did the system clock change?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| J.D |
| Posted: Tue Jan 26, 2010 4:48 pm Post subject: |
|
|
Voyager
Joined: 18 Dec 2009
Posts: 92
Location: United States
|
| It is Cluster-Receiver Channel. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Jan 26, 2010 4:50 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| 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.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mvic |
| Posted: Tue Jan 26, 2010 4:54 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| PeterPotkay wrote: |
| mvic, you are asking about HBINT and not DISCINT? |
 Oops
I meant to ask about DISCINT, not HBINT.
And I see that DISCINT is not mentioned in DIS CHS output. again.
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?
Just guessing... |
|
| Back to top |
|
|
|
|
