| Author |
Message
|
| mattfarney |
 Posted: Fri Feb 19, 2010 2:20 pm Post subject: Problems with channel initiator |
 |
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
Occasionally, I'll find message sitting in a xmitq. Presumably, a trigger was sent to the SYSTEM.CHANNEL.INITQ and processed, but for whatever reason, the channel does not get started.
I had that problem happen today for several channels on the same QM. I looked through the AMQERR##.log files and found no issues related to the channel initiator.
According to the GUI, the channel initiator was running normally (the logs back this up, showing start times from when the QM was recycled.)
I'm just curious if others have seen this odd behavior.
It's not repeatable, but it happens enough that it is not a fluke either.
I've tried populating trigdata with the actual channel name, but the problem isn't repeatable enough to see if that really helped or not.
-mf |
|
| Back to top |
|
 |
| mattfarney |
| Posted: Fri Feb 19, 2010 2:21 pm Post subject: |
|
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
BTW, I've seen this on Windows, Unix, and zOS.
Atm, I think these systems are all 6.0.2
-mf |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Feb 19, 2010 6:39 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If something occasionally has your XMITQ open for MQGETs, maybe only to browse it cuz they are nosy, that makes IPROCS > 0 and that makes MQ triggering not create a trigger messages when an app message hits the queue.
Post your XMITQ definitions.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Feb 20, 2010 7:52 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Presumably, a trigger was sent to the SYSTEM.CHANNEL.INITQ and processed, but for whatever reason, the channel does not get started. |
Presumably? Did you verify this? Did you verify that the xmitq was correctly set for triggering? That the channel initiator app was monitoring the same initq as specified in the xmitq definition? Did any of the trigger messages end up in the dead-letter queue?
What did you check?
_________________
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 |
|
|
| mattfarney |
| Posted: Sun Feb 21, 2010 11:12 am Post subject: |
|
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
So if there are monitoring programs (or people frequently use the MQExplorer), you run the risk of the channel initiator thinking the channel is already running?
How much of a performance hit is it to run as Trigger Every versus Trigger First?
-mf |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Feb 21, 2010 11:34 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| So if there are monitoring programs (or people frequently use the MQExplorer), you run the risk of the channel initiator thinking the channel is already running? |
What? No. The explorer has nothing to do with channel initiators behavior.
Did you create a channel initiator object? Or are you using the runmqchi control program channel initiator?
| Quote: |
| How much of a performance hit is it to run as Trigger Every versus Trigger First? |
If we're still talking about the channel initiator, TrigType(first) is adequate.
If you are contemplating TrigType(every), search here for extensive discussions on this.
_________________
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 |
|
|
| fjb_saper |
| Posted: Sun Feb 21, 2010 2:10 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mattfarney wrote: |
So if there are monitoring programs (or people frequently use the MQExplorer), you run the risk of the channel initiator thinking the channel is already running?
How much of a performance hit is it to run as Trigger Every versus Trigger First?
-mf |
The big question here is did somebody get enable the xmitq for browsing purpose, after stopping the channel? The channel would then have to be started manually. And if the channel gets started manually you better make sure before it gets started that the the ipprocs show 0. Otherwise the system might think the channel is already running....
Depending on the version and fix pack and channel config, I have also seen this type of behavior if the channel name was not in the trigdata of the xmitq, even though it should not be necessary to put it there.
Have fun. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Feb 21, 2010 3:50 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Do not use Trigger Every for channels,
When you say you see a message on the queue, what does that mean? The channel is to running and the message is sitting there and you can browse it? Or the q depth is > 0, the channel may or may not be running, and if you try and look at the message it says there is no message?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mattfarney |
| Posted: Mon Feb 22, 2010 8:49 am Post subject: |
|
|
Disciple
Joined: 17 Jan 2006
Posts: 167
Location: Ohio
|
| fjb_saper wrote: |
Depending on the version and fix pack and channel config, I have also seen this type of behavior if the channel name was not in the trigdata of the xmitq, even though it should not be necessary to put it there.
|
This is what I think I'm seeing. In a couple of environments, I went ahead and filled in the trigdata and the problem did not seem to recur.
Is there any downside to filling the trigdata of the xmitq with the correct channel name?
-mf |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Feb 22, 2010 8:58 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Is there any downside to filling the trigdata of the xmitq with the correct channel name? |
No. This is the documented way to get a channel triggered.
_________________
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 |
|
|
| zonko |
| Posted: Mon Feb 22, 2010 11:41 pm Post subject: |
|
|
Voyager
Joined: 04 Nov 2009
Posts: 78
|
| Quote: |
| if the channel name was not in the trigdata of the xmitq |
This was a bug in v6 GA, which is quite old now! |
|
| Back to top |
|
|
|
|
