| Author |
Message
|
| MikeClark |
 Posted: Mon Feb 23, 2009 10:52 am Post subject: Inactive Sender Channel Question |
 |
|
Apprentice
Joined: 17 Feb 2004
Posts: 27
Location: Olympia, WA
|
--------------------------------------------------------------------------------
I have a situation where messages arrive at a queue manager and are immediately put into a remote queue for further transmission, but the sender queue is inactive, and stays that way. I get a call, check the channel to find it's inactive, and I issue a start. This clears the logjam and it works for a time, but eventually the channel goes inactive again -- and won't start again even though messages are waiting to go out.
The last error log entries for this queue manager were 2 weeks ago. The queue manager is not the only one on this server.
Any ideas?
_________________
"...a long habit of not thinking a thing wrong, gives it a superficial appearance of being right..." [Tom Paine] |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Feb 23, 2009 10:58 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Did you forget to configure channel triggering? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Feb 23, 2009 11:18 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| and are immediately put into a remote queue |
I suppose you mean that the messages arrived on a transmission queue, yes? That's more technically accurate.
_________________
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 |
|
|
| MQEnthu |
| Posted: Mon Feb 23, 2009 8:25 pm Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
| Quote: |
but eventually the channel goes inactive again -- and won't start again even though messages are waiting to go out.
|
You can keep the channel up and running by setting appropriate value in the attribut "Disconnect Interval". You can specify the number of seconds from 0 to 999999. If you set to zero, channel will not disconnect and will wait indefinitely.
However please note that this affects the performance as the resources have to be held up even if they are not used. You can specify heartbeat interval to avoid this. Or configure the channel triggering so that when ever there are messages to be sent across, the channel will be up.
_________________
-----------------------------------------------
It is good to remember the past,
but don't let past capture your future |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Feb 23, 2009 8:51 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
That is not the purpose of heartbeat interval.
Please don't use DISCINT=0 unless you have a very good reason. "I want my channels always running." is NOT a good reason.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| MQEnthu |
| Posted: Mon Feb 23, 2009 9:33 pm Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
AFAIK, when there are no messages on the transmission queue, the sending MCA will send a heartbeat flow to the receiving MCA so as to quiesce the channel without waiting for the disconnect interval to elapse. Please correct me if my understanding is incorrect.
_________________
-----------------------------------------------
It is good to remember the past,
but don't let past capture your future |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Feb 23, 2009 10:10 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| MQEnthu wrote: |
| AFAIK, when there are no messages on the transmission queue, the sending MCA will send a heartbeat flow to the receiving MCA so as to quiesce the channel without waiting for the disconnect interval to elapse. Please correct me if my understanding is incorrect. |
 intercommunication manual 
This is not correct. A running channel will not quiesce before the disconnect interval is reached. At least not for sender/receiver/requester pairs. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| MQEnthu |
| Posted: Mon Feb 23, 2009 10:40 pm Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
A quote from intercommunication manual:
| Quote: |
| A very low value (a few seconds) may cause excessive overhead in constantly starting up the channel. A very large value (more than an hour) could mean that system resources are unnecessarily held up. You can also specify a heartbeat interval, so that when there are no messages on the transmission queue, the sending MCA will send a heartbeat flow to the receiving MCA, thus giving the receiving MCA an opportunity to quiesce the channel without waiting for the disconnect interval to expire. For these two values to work together effectively, the heartbeat interval value must be significantly lower than the disconnect interval value. |
_________________
-----------------------------------------------
It is good to remember the past,
but don't let past capture your future |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Feb 24, 2009 12:36 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
And? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| MQEnthu |
| Posted: Tue Feb 24, 2009 1:03 am Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
| fjb_saper wrote: |
| This is not correct. A running channel will not quiesce before the disconnect interval is reached |
Quote from Intercommunication:
| Quote: |
| A very low value (a few seconds) may cause excessive overhead in constantly starting up the channel. A very large value (more than an hour) could mean that system resources are unnecessarily held up. You can also specify a heartbeat interval, so that when there are no messages on the transmission queue, the sending MCA will send a heartbeat flow to the receiving MCA, thus giving the receiving MCA an opportunity to quiesce the channel without waiting for the disconnect interval to expire. For these two values to work together effectively, the heartbeat interval value must be significantly lower than the disconnect interval value |
_________________
-----------------------------------------------
It is good to remember the past,
but don't let past capture your future |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Feb 24, 2009 7:19 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If the RCVR channel doesn't get the expected Heartbeat, it knows the other side is "gone" and no longer has to keep the socket open, waiting for more heartbeats or messages that may never come. The "orphaned" RCVR channel can now quiesce without waiting for DISCINT.
Heartbeats themselves do not cause a channel to shutfown if things are fine and the DISCINT has not been reached.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
