| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Strange case with sender and receiver in inactive state |
« View previous topic :: View next topic » |
| Author |
Message
|
| jefflowrey |
 Posted: Thu Jan 08, 2004 11:01 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I believe (although I could be wrong about this), DISCINT = 0 means that the channel won't disconnect, not that it's going to be connected all the time.
So, I believe it's normal for a channel with DISCINT = 0 to be inactive after QM startup, if it hasn't connected yet.
Also, it is perfectly normal for a channel not to start up when a message goes into an XMIT queue, provided the XMIT queue is not set up to trigger the channel.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| JasonE |
| Posted: Fri Jan 09, 2004 1:53 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
| To add to the previous update, only MQ channels required for clustering trigger by default |
|
| Back to top |
|
|
| balaji sr |
| Posted: Fri Jan 09, 2004 2:15 am Post subject: |
|
|
Apprentice
Joined: 07 Jan 2003
Posts: 28
|
If DISCINT is set to zero means the message channel agent to wait indefinitely.
Second question: how does it possible that sender do not start transmission on action 3 (state was inactive and channel initiator of qmgr1 was running!!) ?
>> Set the channels for auto startup and check.
4) When i stop / start the channel sender qmgr1.qmgr2, it works (message goes to qmgr2)
>> If there is a message in the XMIT queue & if the channel is not running, you have to stop & start the channel.
--bala |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
