| Author |
Message
|
| velocity |
 Posted: Tue Aug 11, 2009 8:40 am Post subject: Sender channel not starting/triggering |
 |
|
Centurion
Joined: 30 Nov 2007
Posts: 126
|
I have remote queuing architecture where a remote queue defn on QM A is pointing to a queue on QM B. Xmitq is set up for triggering the sender channel.
I see the msgs are still stuck in the XMITQ.. I have checked everything looks good...Any ideas as to why channel is not starting..?
BTW - If I manually start the channel..it runs fine.. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Aug 11, 2009 8:59 am Post subject: Re: Sender channel not starting/triggering |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| velocity wrote: |
| I have checked everything looks good... |
Well clearly everything isn't..... 
| velocity wrote: |
| Any ideas as to why channel is not starting..? |
Triggering information improperly set? (You don't mention what version of WMQ you're using)
Channel initiator not running?
FDCs or logs?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| velocity |
| Posted: Tue Aug 11, 2009 9:12 am Post subject: |
|
|
Centurion
Joined: 30 Nov 2007
Posts: 126
|
Mq Version: 6.0.2.3
SYSTEM.CHANNEL.INITQ is defined on the xmitq.
Trigger data is the sender channel name.
xmitq is named same as remote qmname.
I believe on version 6 when the qmanager starts the channel initiator starts too..I know how to start the channel initiator..but dont know how to make sure it is running or not..
Pls advice..
Thank you. |
|
| Back to top |
|
|
| velocity |
| Posted: Tue Aug 11, 2009 10:27 am Post subject: |
|
|
Centurion
Joined: 30 Nov 2007
Posts: 126
|
| I got it..The target queue name was incorrect. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Aug 11, 2009 11:32 am Post subject: Re: Sender channel not starting/triggering |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| velocity wrote: |
| ...I have checked everything looks good... |
The 'target' queue being the XMITQ? When triggering problems occur, check, double check, then have somebody else QA it. All too frequently I see what I expect to see, not what is there.
_________________
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 |
|
|
| Mr Butcher |
| Posted: Tue Aug 11, 2009 10:07 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
| velocity wrote: |
| I got it..The target queue name was incorrect. |
the target queue (rname) in the remoteq definition? this can not be the reason for triggering not working, as it is only used on the receiving queuemanager. the name of the xmitq is the relevant part on the sending queuemanager.
_________________
Regards, Butcher |
|
| Back to top |
|
|
| velocity |
| Posted: Wed Aug 12, 2009 3:03 pm Post subject: |
|
|
Centurion
Joined: 30 Nov 2007
Posts: 126
|
Yes..Target queue meaning RNAME and target QM meaning RQMNAME..both were incorrect.
The moment both were changed to the correct values the channel started.
Wonder why the channel wouldnt start when RNAME and RQMNAME were incorrect. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 12, 2009 3:11 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| velocity wrote: |
Yes..Target queue meaning RNAME and target QM meaning RQMNAME..both were incorrect.
The moment both were changed to the correct values the channel started.
Wonder why the channel wouldnt start when RNAME and RQMNAME were incorrect. |
The only thing I can think of, is that you are in a cluster and did not specify an xmitq to your remote queue.
The channel would not have started as there was no message for the channel to process.
Do you have a default xmitq defined?
Did you get a good return from the MQPUT?
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| velocity |
| Posted: Wed Aug 12, 2009 3:21 pm Post subject: |
|
|
Centurion
Joined: 30 Nov 2007
Posts: 126
|
| Quote: |
The only thing I can think of, is that you are in a cluster and did not specify an xmitq to your remote queue.
The channel would not have started as there was no message for the channel to process.
Do you have a default xmitq defined? |
I was using classic SDR RCVR channels with xmitq defined wite he same of the remote QMNAME.
| Quote: |
| Did you get a good return from the MQPUT? |
I think the msgs (which were stuck in the xmitq) were transported in the remote QM's DLQ, since the wrong channel started. Thats all I can think of. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 12, 2009 8:35 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| velocity wrote: |
I was using classic SDR RCVR channels with xmitq defined wite he same of the remote QMNAME.
| Quote: |
| Did you get a good return from the MQPUT? |
I think the msgs (which were stuck in the xmitq) were transported in the remote QM's DLQ, since the wrong channel started. Thats all I can think of. |
That would explain it.
My assumption was that the channel attached to the xmitq did not start... very unlikely hence the assumption that you were in a cluster...
But yes if you had the wrong name for qmgr or queue the message would eventually land in a DLQ somewhere along the multihop path... But the channel using the xmitq defined in the remote queue was running... the message just never showed up where you expected it...
Welcome to the art of building an MQ network.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
