| Author |
Message
|
| AYSC |
 Posted: Wed Jul 13, 2005 6:09 am Post subject: |
 |
|
Newbie
Joined: 12 Jul 2005
Posts: 8
|
still investigating
i'll keep you posted, to busy right now.
wasn't queue problem
i've removed the queue, the flow restarted and then blocked again
the same flow in another env works just fine with the same messages.
starting to think that we are dealing with a configuration problem. |
|
| Back to top |
|
 |
| markhiscock |
| Posted: Wed Jul 13, 2005 11:58 pm Post subject: |
|
|
Novice
Joined: 16 May 2005
Posts: 22
Location: IBM Hursley, UK
|
My apologies if this is a simple question and you have covered this, but your error suggests that your input node cannot open the input queue to get messages.
Is the Queue property of the Input node set correctly? I.e. is it pointing at the right queue?
Just want to eliminate all possibilities!
Cheers,
Mark |
|
| Back to top |
|
|
| mqperson |
| Posted: Wed Jan 11, 2006 10:20 am Post subject: |
|
|
Apprentice
Joined: 10 Jan 2006
Posts: 32
|
did a redeploy of the BAR file resolve this issue ? we are facing the exact same issue on one of the production AIX boxes.
thanks... |
|
| Back to top |
|
|
| mqperson |
| Posted: Mon Aug 21, 2006 1:13 pm Post subject: |
|
|
Apprentice
Joined: 10 Jan 2006
Posts: 32
|
we investigated this issue over the last few months. firstly, we upgraded to the latest CSD - that reduced the frequency of the issue. then fruther investigation revealed that it could be a problem with one of the plugins in the flow. we have now upgraded to the latest version of the plugin and things have been silent so far. touch wood  . |
|
| Back to top |
|
|
| BrisVegas |
| Posted: Mon Aug 21, 2006 6:03 pm Post subject: |
|
|
Novice
Joined: 05 Aug 2004
Posts: 14
Location: Brisbane, Australia
|
mqperson - when you say the latest CSD.... do you mean the WBIMB5 CSD's?? Or are you talking about Websphere MQ?
We've started getting this type of situation this past week. Haven't quite figured out what action has gotten things moving again, but have tried:-
turning trace on for the execution group
stopping and starting the execution group
stopping and starting the Config Mgr and Broker
backing up and restoring the Input queue
Have managed to get messages flowing again each tiem using one or more of the above, but haven't been able to get any trace out of a dumplog yet, as they start flowing successfully once they are polled from the input queue...
weird! |
|
| Back to top |
|
|
| mqperson |
| Posted: Wed Aug 23, 2006 2:29 pm Post subject: |
|
|
Apprentice
Joined: 10 Jan 2006
Posts: 32
|
Per IBM recommendation (and our MQ instincts ), we upgraded WBIMB5.0 from CSD03 to CSD07. That reduced the frequency of this issue. We dont have the queue backup issue anymore, but occasionally the execution group restarts itself for some messages. But again, that happens very infrequently. So we are happy with CSD07.
Does your flow use any plugins/supportpacs ? |
|
| Back to top |
|
|
|
|
