| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Changing TRIGGER attribute |
« View previous topic :: View next topic » |
| Author |
Message
|
| fitzcaraldo |
 Posted: Sun Sep 25, 2005 5:41 pm Post subject: Changing TRIGGER attribute |
 |
|
Voyager
Joined: 05 May 2003
Posts: 98
|
I have a test queue manager configured as a gateway with many channels definitions(thousands). I use triggered XMIT queues to start the channels as required. These are all TRIGGER, TRIGTYPE(FIRST) TRIGDATA(channelname) TRIGDEPTH(1).
The problem I am seeing is that some of these XMITQ queue spontaneously change to NOTRIGGER and I trying to work out why. I was told by someone who knows more than me that this can occur when channel failures happen.
This seems reasonable but I'm having a hard time to find any reference to this in the Intercoms manual. Does anyone know the circumstances when this will occur or point me to the doco for this is? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Sep 25, 2005 8:19 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If there is no DLQ on the target qmgr and the target queue is full the channel will stop.
Check out the manuals on channels (intercommunication) and you should find all the possibilities that put the channel into stopped mode.
Enjoy  |
|
| Back to top |
|
|
| hopsala |
| Posted: Sun Sep 25, 2005 8:44 pm Post subject: Re: Changing TRIGGER attribute |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| fitzcaraldo wrote: |
The problem I am seeing is that some of these XMITQ queue spontaneously change to NOTRIGGER and I trying to work out why. I was told by someone who knows more than me that this can occur when channel failures happen.
This seems reasonable but I'm having a hard time to find any reference to this in the Intercoms manual. Does anyone know the circumstances when this will occur or point me to the doco for this is? |
| In the Intercommunication Manual, chapter 48, the prophet wrote: |
If a triggered channel refuses to run, the possibility of in-doubt messages should be investigated as described above.
Another possibility is that the trigger control parameter on the transmission queue has been set to NOTRIGGER by the channel. This happens when:
v There is a channel error
v The channel was stopped because of a request from the receiver
v The channel was stopped because of a problem on the sender that requires manual intervention |
Not very descriptive I agree... Generally speaking I can say that from my experience every time a channel goes to STOPPED it applies NOTRIGGER, but this seems a bit odd since STOPPED channels can't be triggered anyway, so why disable triggering?
Possibly this is to prevent someone from having an in-doubt channel in retry and running STOP CHL(X) STATUS(INACTIVE) thus triggering the channel once more. However, the worst that could happen is simply that the channel returns to retry, so I don't think that's it.
Apparently, by a description given in Triggered channel did not start. which I dug up, there are certain (emphirical, but yet to be explained) scenarios in which an error causes a channel to go to INACTIVE instead of some other state; if this is so, it would indeed make sense to disable triggering, but why on earth should an erroneous channel go to INACTIVE??
I searched the archives and manuals profusely, and although I found several sightings the said behavior (see Sender don't start) but regarding any answers I came out empty handed.
Any ideas anyone?
(p.s fitz - the parameter TRIGDEPTH only applies to TRIGTYPE(DEPTH))
Last edited by hopsala on Sun Sep 25, 2005 9:10 pm; edited 2 times in total |
|
| Back to top |
|
|
| hopsala |
| Posted: Sun Sep 25, 2005 8:46 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| fjb_saper wrote: |
| If there is no DLQ on the target qmgr and the target queue is full the channel will stop. |
As I said in my post (didn't see your post until after I posted) a STOPPED channel cannot be triggered by runmqchi; admittedly I can't seem to able to find it in the manuals, but experience and a small experiment I just made here shows this to be true. If you try triggering a stopped chl you'll get
| Quote: |
AMQ9534: Channel 'SNUHY.LUSHY' is currently not enabled.
EXPLANATION:
The channel program ended because the channel is currently not enabled.
ACTION:
Issue the START CHANNEL command to re-enable the channel. |
regardless of TRIGGER or NOTRIGGER... |
|
| Back to top |
|
|
| fitzcaraldo |
| Posted: Sun Sep 25, 2005 9:35 pm Post subject: |
|
|
Voyager
Joined: 05 May 2003
Posts: 98
|
I did have some full queues but I always had a dead letter queue so not sure that explains it.
...But I did run out of disk space on my data file system which I imagine had the same effect - ie couldn't write to the destination queue 'cos the disk was full so tried to write to the dead letter queue and couldn't 'cos the disk was full.... |
|
| 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
|
|
|
|
