| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TRIGGERING |
« View previous topic :: View next topic » |
| Author |
Message
|
| joehill |
 Posted: Wed Nov 15, 2006 5:23 am Post subject: TRIGGERING |
 |
|
Newbie
Joined: 14 Nov 2006
Posts: 7
Location: Sweden
|
Hi,
Whay is MQ verssion 6 setting my trigg contyrol to off in my transmission queue, I changed it to on but after a while it changed to off again?
Also in version 5.3 in the field "initation queue" you could choose between all transmission queue,s and the SYSTEM CHANNEL INIT Q, in 5.3 I allwys choose SYSTEM CHANNEL INIT Q, worked ok, but in 6.0 there is nothing to choose from, I just typed in SYSTEM CHANNEL Q, is that ok or do I have to change to something else?
PLS HELP
/Joe |
|
| Back to top |
|
 |
| kevinf2349 |
| Posted: Wed Nov 15, 2006 5:26 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Is the remote queue full? |
|
| Back to top |
|
|
| joehill |
| Posted: Wed Nov 15, 2006 5:49 am Post subject: |
|
|
Newbie
Joined: 14 Nov 2006
Posts: 7
Location: Sweden
|
| kevinf2349 wrote: |
| Is the remote queue full? |
Well, I dont know right now, but the sender channel in my QMGR is in "retrying" and in doubt status, and have 7 messages not sent. This morning the channel also was in "doubt" status, I did a resolve (this is just test now, and this have never worked) and started the channel which came up running, by then I didn't check if the trig control was set to off at that time, then we tryed to send a message, but it ended up in the status described above. Running w2k3.
/Joe |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Wed Nov 15, 2006 6:12 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
if a channel goes into retry or is stopped the xmitq is changed to trigger off and get disabled. so this is not a matter of your trigger definitions (if they worked before).
if the channel is started trigger is set back to on and the xmit get enabled.
you should check why your channel goes into retry state by checking your mqseries log and the log of the remote queuemanager you are trying to send to
(most likely in this case is that the remote queuemanager has a problem and no dlq defined (or the dlq is full))
_________________
Regards, Butcher |
|
| Back to top |
|
|
| joehill |
| Posted: Wed Nov 15, 2006 6:35 am Post subject: |
|
|
Newbie
Joined: 14 Nov 2006
Posts: 7
Location: Sweden
|
| Mr Butcher wrote: |
if a channel goes into retry or is stopped the xmitq is changed to trigger off and get disabled. so this is not a matter of your trigger definitions (if they worked before).
if the channel is started trigger is set back to on and the xmit get enabled.
you should check why your channel goes into retry state by checking your mqseries log and the log of the remote queuemanager you are trying to send to
(most likely in this case is that the remote queuemanager has a problem and no dlq defined (or the dlq is full)) |
Well, it's working now, the problem was that I had to do a reset of the channel, probably becouse they were off sync.
Thank,s for yor reply. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Wed Nov 15, 2006 6:38 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Quote: |
probably becouse they were off sync.
|
Now the task is to find out why they were 'off sync'  |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
