ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Triggered channel did not start.

Post new topic  Reply to topic
 Triggered channel did not start. « View previous topic :: View next topic » 
Author Message
csmith28
PostPosted: Mon Nov 29, 2004 3:33 pm    Post subject: Triggered channel did not start. Reply with quote

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

OK, here goes,

AIX5.1.0.0
WQM 5.3.0.6

One MQManager on the Server.

The SDR channel in question is connecting zOS MQManager running Version 5.2.0.*.

The issue is, even though the XMITQ was/is set to:

PROCESS(PROCESS.NAME) * PROCESS points to the Sender channel.
INITQ(SYSTEM.CHANNEL.INITQ)
TRIGGER
TRIGTYPE(FIRST)
TRIGDPTH(1)

The channel is set to:

SHORTRTY(10)
SHORTTMR(60)
LONGRTY(999999999)
LONGTMR(1200)

The SDR channel was in and INACTIVE status even though there were over 5000 messages sitting on the XMITQ.

Now, 24 hours previouse to this there were two incidents that would have prevented the channel from starting normally. Yeah, it was a long holiday weekend.

A. A code deploy on three remote Client Application Servers created an issue in which the MaxActiveChannel Threshold was reached on the MQManager.

B. As a result of problem A it was later discovered that I had run out of Shared Memory resources due to stale connections.

See http://www.mqseries.net/phpBB2/viewtopic.php?t=19108 gripe session for more details.

What is bothering me is that, if the channel was TRIGGERED during either of these events I would expect the channel to have a status of RETRY but it was clearly in an INACTIVE state.

Unfortunately I did not get an opportunity to display the attributes of the XMITQ before a third party took action to correct the issue and oddly enough this third party didn't simply issue a start chl for the SDR Channel in question. What he did was, via MQExplore, alter the XMITQ to NOTRIGGER then immediatly back to TRIGGER and the SDR Channel started.....

Why was the channel status INACTIVE? It just doesn't make any sense to me.

* This channel and XMIT Queue were created before I started here. I know that I don't have to use the PROCESS(PROCESS.NAME) attribute and that I can put the SDR Channel name in the TRIGDATA field but I haven't had the chance to change it.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Mon Nov 29, 2004 7:25 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Here's a guess:
Channels are triggered OnFirst meaning the queue depth of the XMITQ has to go from 0 to 1. If for some reason the trigger did not happen when the depth did go from 0 to 1 (there are ways it can happen), the XMITQ would continue to pile up and not trigger as the depth went from 1 to 2, 2 to 3, etc.

The Trigger Interval attribute of the QM will save you here. If you left it at the default of 99999999999, it cant help. I have mine set to 300000 (5 minutes).

If TriggerInterval was set to a good value, then we have to keep poking, but I bet that was it.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
csmith28
PostPosted: Mon Nov 29, 2004 9:51 pm    Post subject: Reply with quote

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

Odd, I would expect TRIGINT to be an attribute of the XMITQ but apparently it is an attribute of the qmgr.

Just wondering, are changes to that attribute dynamic or does the qmgr need to be stopped an restarted before the change takes affect?
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.
Back to top
View user's profile Send private message
Nigelg
PostPosted: Tue Nov 30, 2004 2:06 am    Post subject: Reply with quote

Grand Master

Joined: 02 Aug 2004
Posts: 1046

You have to recycle the qmgr for changes to TRIGINT to take effect.
Back to top
View user's profile Send private message
knegarpetter
PostPosted: Tue Dec 14, 2004 6:25 am    Post subject: Reply with quote

Apprentice

Joined: 10 Dec 2004
Posts: 39

what do you meen by: recycle??

Petter
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Dec 14, 2004 6:33 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

"Recycle" means... stop and then start, in this context.

Occasionally, you need to recycle a queue manager by deleting it and recreating it... (recycling the bits... )
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
csmith28
PostPosted: Tue Dec 14, 2004 2:46 pm    Post subject: Reply with quote

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

jefflowrey wrote:
"Recycle" means... stop and then start, in this context.

Occasionally, you need to recycle a queue manager by deleting it and recreating it... (recycling the bits... )


Reminds me, once I was asked by a PM to "reboot" the WebSphere Server... So I was thinking # shutdown -Fr,... to reboot the AIX Server were the WebSphere Application was installed/running.

Under the circumstances I thought rebooting the Server was a bit extreem so I cautiously asked for clarification. Turns out he wanted me to stop and restart WebSphere. I was glad I asked.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.


Last edited by csmith28 on Tue Dec 14, 2004 6:59 pm; edited 1 time in total
Back to top
View user's profile Send private message
WannaBeInAParker
PostPosted: Tue Dec 14, 2004 2:48 pm    Post subject: Reply with quote

Voyager

Joined: 09 Dec 2003
Posts: 81

Yes, always ask for clarification.

I love when our users ask for a queue manager to be rebooted.

heheheh
_________________
-WannaBe-
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Triggered channel did not start.
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.