| Author |
Message
|
| srinivasraom |
 Posted: Sun Oct 15, 2006 11:50 pm Post subject: Tansmission Queue Not Triggering The Channel |
 |
|
Apprentice
Joined: 18 May 2006
Posts: 31
|
Hi,
I sending messages from one queue manager to another queue manger or remote machine. this was happening with a channel through transmission queue and a remote queue.
The problem is every time i need to explicitly start the channel to see the messages in the remote box. By default the transmission queue should be able to trigger the channel , which was not happening.
Can anyone guess why is happening like this.
Regards
Srinivas |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Mon Oct 16, 2006 12:02 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
did you set up the trigger options for the transmission queue? please post a display of the xmitq (all attributes)
is the channel initiator running?
if the answer to one of the questions is "no" or "dont know" or "what is this" then read the intercommunication guide.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| srinivasraom |
| Posted: Mon Oct 16, 2006 12:33 am Post subject: |
|
|
Apprentice
Joined: 18 May 2006
Posts: 31
|
Thanks for the reply.
Please check the below given output.
dis queue(XMTQ_HKWTI1S1)
7 : dis queue(XMTQ_HKWTI1S1)
AMQ8409: Display Queue details.
DESCR(Transmission queue for Trade TI to Message Translator)
PROCESS( ) BOQNAME( )
INITQ( ) TRIGDATA( )
CLUSTER( ) CLUSNL( )
QUEUE(XMTQ_HKWTI1S1) CRDATE(2006-10-04)
CRTIME(19.45.32) ALTDATE(2006-10-16)
ALTTIME(14.44.12) GET(ENABLED)
PUT(ENABLED) DEFPRTY(0)
DEFPSIST(NO) MAXDEPTH(5000)
MAXMSGL(4194304) BOTHRESH(0)
SHARE DEFSOPT(SHARED)
HARDENBO MSGDLVSQ(PRIORITY)
RETINTVL(999999999) USAGE(XMITQ)
TRIGGER TRIGTYPE(FIRST)
TRIGDPTH(1) TRIGMPRI(0)
QDEPTHHI(80) QDEPTHLO(20)
QDPMAXEV(ENABLED) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QSVCINT(999999999)
QSVCIEV(NONE) DISTL(YES)
NPMCLASS(NORMAL) DEFTYPE(PREDEFINED)
TYPE(QLOCAL) SCOPE(QMGR)
DEFBIND(OPEN) IPPROCS(0)
OPPROCS(0) CURDEPTH(0) |
|
| Back to top |
|
|
| Nigelg |
| Posted: Mon Oct 16, 2006 2:07 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
set INITQ to be SYSTEM.CHANNEL.INITQ
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| srinivasraom |
| Posted: Mon Oct 16, 2006 2:54 am Post subject: |
|
|
Apprentice
Joined: 18 May 2006
Posts: 31
|
In transmission queue definition, if no init queue specified, then it should take default init queue right?
How does this will solve the problem? |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Mon Oct 16, 2006 3:27 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
imho the channel initiator is triggered by the SYSTEM.CHANNEL.INITQ
_________________
Regards, Butcher |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 16, 2006 3:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| srinivasraom wrote: |
| In transmission queue definition, if no init queue specified, then it should take default init queue right? |
Where is this behaviour documented? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| srinivasraom |
| Posted: Mon Oct 16, 2006 4:03 am Post subject: |
|
|
Apprentice
Joined: 18 May 2006
Posts: 31
|
| Please refer to Websphere MQ Intercommunication document, where they told SYSTEM.CHANNEL.INITQ as default initiation queue. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 16, 2006 4:14 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Yes, but where does it say (in the Intercommuncation guide or elsewhere)that if no init queue is specified the INITQ parameter defaults to SYSTEM.CHANNEL.INITQ? It certainly says that this object is created as part of the installation as the default initq, it also says that the channel initiator will use it as the default if none is specifed but I can't find a reference to it being copied into the queue definition if left blank.
This doesn't mean it isn't of course, just that I can find it.
It's also easily proved by using the suggestion - put it in the XMITQ definition. If it starts working, it wasn't defaulting. If it stays not working it's made no difference.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| srinivasraom |
| Posted: Mon Oct 16, 2006 4:22 am Post subject: |
|
|
Apprentice
Joined: 18 May 2006
Posts: 31
|
| It is also documented in Websphere MQ System Administration guide |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 16, 2006 4:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Nope, still can't find it. Just the reference to the channel initiator using it as a default, no reference to it being a default on an XMITQ. Still, going through a bad patch atm - brain somewhat soggy 
Clearly there's a different root cause for your problem then if the XMITQ is picking up the default name even though it's shown as blank in the display. I wish you success in tracking it down, but have no additional suggestions to make. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
