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 » Messages stuck in Transmission Queue

Post new topic  Reply to topic Goto page Previous  1, 2, 3, 4  Next
 Messages stuck in Transmission Queue « View previous topic :: View next topic » 
Author Message
mqjeff
PostPosted: Thu Feb 10, 2011 7:54 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Vitor wrote:
bruce2359 wrote:
Long ago I ran out of fingers, toes and patience, counting the number of times it was "the network" despite denial by the network support team.


I think this is the first time we've got such a widely experienced phenomenon.


I riposte with "MQ Is Broken!".
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Feb 10, 2011 8:02 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

mqjeff wrote:
Vitor wrote:
bruce2359 wrote:
Long ago I ran out of fingers, toes and patience, counting the number of times it was "the network" despite denial by the network support team.


I think this is the first time we've got such a widely experienced phenomenon.


I riposte with "MQ Is Broken!".




I think this coffee is decaff.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Thu Feb 10, 2011 8:16 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.

Vitor wrote:

I riposte with "MQ Is Broken!".

My favorite: "The Internet must be down."
_________________
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
View user's profile Send private message
Navya
PostPosted: Thu Feb 17, 2011 3:28 am    Post subject: Reply with quote

Novice

Joined: 03 Feb 2011
Posts: 15

Hi,

Fortunately, after Network team's action, the queue manger is back to normal except one weird behaviour, this time im confident it is not related to Networks.

Messages are stucking in the Transmission Q, till i start the Sender channel. I can't see any messages in the 'SYSTEM.CHANNEL.INITQ'. and also no logs to say channel is started. Receiver channels are getting started automatically, i mean i am able receive the messages.

I can see a reader on 'SYSTEM.CHANNEL.INITQ' , so i think the transmission queue is not creating a trigger message.

Trasmission queue definition below :
Quote:

DEFINE QLOCAL('XX') +
ACCTQ(QMGR) +
BOQNAME(' ') +
BOTHRESH(0) +
CLUSNL(' ') +
CLUSTER(' ') +
CLWLPRTY(0) +
CLWLRANK(0) +
CLWLUSEQ(LOCAL) +
DEFBIND(OPEN) +
DEFPRTY(0) +
DEFPSIST(NO) +
DEFSOPT(SHARED) +
DESCR('Transmission Queue') +
GET(ENABLED) +
HARDENBO +
INITQ('SYSTEM.CHANNEL.INITQ') +
MAXDEPTH(5000) +
MAXMSGL(4194304) +
MONQ(QMGR) +
MSGDLVSQ(PRIORITY) +
TRIGGER +
NPMCLASS(NORMAL) +
PROCESS(' ') +
PUT(ENABLED) +
QDEPTHHI(80) +
QDEPTHLO(20) +
QDPHIEV(DISABLED) +
QDPLOEV(DISABLED) +
QDPMAXEV(ENABLED) +
QSVCIEV(NONE) +
QSVCINT(999999999) +
RETINTVL(999999999) +
SCOPE(QMGR) +
SHARE +
STATQ(QMGR) +
TRIGDATA(' ') +
TRIGDPTH(1) +
TRIGMPRI(0) +
TRIGTYPE(FIRST) +
USAGE(Xmitq) +
REPLACE
Back to top
View user's profile Send private message
exerk
PostPosted: Thu Feb 17, 2011 3:51 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Free fish - out the channel name in TRIGDATA, set the trigger on the XMITQ to NOTRIGGER, then back to TRIGGER.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
Navya
PostPosted: Thu Feb 17, 2011 4:21 am    Post subject: Reply with quote

Novice

Joined: 03 Feb 2011
Posts: 15

No change even after Notrigger then Trigger.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Thu Feb 17, 2011 6:06 am    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.

TRIGDATA('the name of the channel to start goes here ') +
_________________
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
View user's profile Send private message
Navya
PostPosted: Thu Feb 17, 2011 6:16 am    Post subject: Reply with quote

Novice

Joined: 03 Feb 2011
Posts: 15

Thank you very much, it worked.

But the channel is working from ages, not working only from 2 days.
As far i know no one changed the channel definition recently .

Thats why i was not checkingthe channel definition.

Thank u
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Feb 17, 2011 6:19 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Navya wrote:
As far i know no one changed the channel definition recently .


Guess again.

Then check your security & change the password to the mqm user.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Navya
PostPosted: Thu Feb 17, 2011 6:41 am    Post subject: Reply with quote

Novice

Joined: 03 Feb 2011
Posts: 15

To My Surprises,

Most of our transmission queues in Many queue managers don't have TRIGDATA set to Channel Name.

But they are all working.

So As i said the channel is not changed from ages but it was before this n/w problem and it worked when switch on a backup n/w.

It again stopped when they switched back to Main Network line.

Though it may not be related.
But even now Transmission queue should work though TRIGDATA is not set.

Thanks,
Back to top
View user's profile Send private message
skoobee
PostPosted: Thu Feb 17, 2011 6:57 am    Post subject: Reply with quote

Acolyte

Joined: 26 Nov 2010
Posts: 52

[quote]put the channel name in TRIGDATA[/quote]

You do not have to do that, not for a long time now (perhaps MQSeries 5.2?).

The channel initiator looks for a channel which has the queue in its XMITQ attribute.
Back to top
View user's profile Send private message
Navya
PostPosted: Thu Feb 17, 2011 7:09 am    Post subject: Reply with quote

Novice

Joined: 03 Feb 2011
Posts: 15

I do agree but some how it stopped working after a n/w change in our queue manager which is version 6.0.

May have read more about how it works
Back to top
View user's profile Send private message
JosephGramig
PostPosted: Thu Feb 17, 2011 7:29 am    Post subject: Reply with quote

Grand Master

Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA

skoobee wrote:
exerk wrote:
put the channel name in TRIGDATA


You do not have to do that, not for a long time now (perhaps MQSeries 5.2?).

The channel initiator looks for a channel which has the queue in its XMITQ attribute.


True... http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.csqzae.doc/ic12530_.htm

I've never tried that. I see mixed case for 'USAGE(Xmitq)' in your output. I have V7.0.1.3 on Windows and can't get it to take that. Maybe your version has a bug and allows that. What does dspmqver say and what OS is this?
Back to top
View user's profile Send private message AIM Address
Navya
PostPosted: Thu Feb 17, 2011 7:30 am    Post subject: Reply with quote

Novice

Joined: 03 Feb 2011
Posts: 15

IBM says they have fixed this issue in 6.0.1 but it doesn't seems to be.

I will let it work for a while and upgrage MQ when ever possible.

Thank you all ur time
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Feb 17, 2011 7:35 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Navya wrote:
IBM says they have fixed this issue in 6.0.1 but it doesn't seems to be.

I will let it work for a while and upgrage MQ when ever possible.

Thank you all ur time

Don't! Upgrade right away. You really should be @ 6.0.2.10 or above or @ 7.0.1.4....
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2, 3, 4  Next Page 3 of 4

MQSeries.net Forum Index » General IBM MQ Support » Messages stuck in Transmission Queue
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.