| Author |
Message
|
| JRome |
 Posted: Wed Nov 09, 2011 4:24 am Post subject: Message flows unresponsive to operations through Toolkit |
 |
|
Novice
Joined: 01 Jul 2011
Posts: 15
|
Let me first explain the environment
We have two sets of brokers running in two different geological locations having it's two seperated config managers where we have the developer toolkit as well.
We are running broker V6.0.
We have also the API Proxy exerciser where the config manager, toolkit is.
The brokers are configred to DB2 database (broker database)
We have Tivoly omegamon agents running on the brokers as well for monitoring perposes.
As you know there is a queue manager on each of the config managers.
Currently we are observing the following behaviour:
When we try to stop a running message flow through the toolkit, on either of the config managers we are getting the response of a success, but we cannot see the '!' mark against the flow we stopped.
Even afer we refreshed the message flow concerned through the tool kit, the API proxy exerciser and then tried to stop the message flow through the tool kit
we still get the same results as above.
On certain flows when we try to stop, it is stopping, but when we bring it up it gives a success response, but it is not realy running, we could confirm througth Tivoly omegamon that this flow is running, the proxy exerciser also shows that this process is running, but actually the this specific flow is stopped, because the messages are not getting transformned we see all the simptoms of it's being stopped.
And there are no duplicate flows found.
How do we find out the "correct" status of the message flow.
Will the Broker database have the correct information about the status of the message flow.
I have to find out which table will have the status information of the flow.
What should I do to make the toolkit control the message flow better.
Unfortunatly it is WMB V7.0/ > has the command to stop a flow through broker commandline.
Thanks for the help. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Nov 09, 2011 4:27 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
What fixpack of V6.0 are you running?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Nov 09, 2011 4:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Level 2 support used to have a manual process that could be gone through to sync the configmgr and broker databases in v6.
This happens automatically in v6.1 and later.
You are out of support at v6.0 unless you have a seriously extended contract, so you can't get any assistance from L2 on this.
You need to take this opportunity to push for migration to v7.
But the failure or success of a flow to start should be completely logged in the Broker system log. particularly at later fixpacs of v6.0 - so if you're not at a FP within one or two of the last, please DO UPDATE. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Nov 09, 2011 8:10 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
This could actually be a symptom of another flow having a problem in the same eg...
- Does the display refresh correctly if you kill the eg? (i.e. it gets restarted by the broker).
- Is your xlC_Route at the right level?.
- Do you see memory leeks on the e.g's?
- Do you have a flow in an endless loop in the e.g.?
Note that if the broker is busy, it may take some time...
What other observations for the same e.g. do you have 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| JRome |
| Posted: Wed Nov 09, 2011 8:46 pm Post subject: |
|
|
Novice
Joined: 01 Jul 2011
Posts: 15
|
Our WMB Version is 6.0.2
Level 2 support used to have a manual process that could be gone through to sync the configmgr and broker databases in v6.
mqjeff can you get me the manual process- steps that you mentioned above for me please, thanks. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Nov 09, 2011 9:43 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Delete all flows from the e.g. and redeploy...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 10, 2011 2:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| JRome wrote: |
| mqjeff can you get me the manual process- steps that you mentioned above for me please, thanks. |
No. |
|
| Back to top |
|
|
| JRome |
| Posted: Thu Nov 10, 2011 3:31 am Post subject: |
|
|
Novice
Joined: 01 Jul 2011
Posts: 15
|
| We will be upgrading to V7 very soon (first quarter next year). |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 10, 2011 5:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| JRome wrote: |
| We will be upgrading to V7 very soon (first quarter next year). |
 
In the meantime, you need to explain that you've hit a situation that requires you to recreate the broker and configmgr.
And that if you had upgraded last year, you wouldn't have hit this situation and if you *did* run into it, you would still be under support and thus able to get help to FIX it instead of having to recreate everything. |
|
| Back to top |
|
|
|
|
