| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message flow is not in Sync with Toolkit and the Broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| james |
 Posted: Mon Aug 29, 2005 10:32 am Post subject: Message flow is not in Sync with Toolkit and the Broker |
 |
|
Novice
Joined: 10 Jan 2003
Posts: 18
|
Hi,
I have deployed a message flow to the broker and later deleted it. In the toolkit it disappeared and the flow is showing that it is still deployed to the broker. Right now the tool kit and the broker are not in Sync. Inorder to rectify this could anyone of you please help me which broker tables i need to look into and what re the steps i need to follow?
Thanks in Advance...
JAMES  |
|
| Back to top |
|
 |
| JT |
| Posted: Mon Aug 29, 2005 11:04 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Before you start messing with the broker database, try issuing a mqsireload of the execution group on the broker server. |
|
| Back to top |
|
|
| james |
| Posted: Mon Aug 29, 2005 1:12 pm Post subject: |
|
|
Novice
Joined: 10 Jan 2003
Posts: 18
|
Thanks. That worked but all the message flows that were in that execution group has been stopped. This problem is occuring since long time. Is there a problem with mqsireload in WBIMB.
Thanks,
James |
|
| Back to top |
|
|
| JT |
| Posted: Mon Aug 29, 2005 2:23 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
I personally have never encountered any issues with the mqsireload command.
According to the documentation your message flows should have restarted. I can attest that this is the normal behaviour.
| Quote: |
Because an execution group does not stop until all message flows within it terminates, the ability of the broker to reload quickly depends on the processing time for the longest running message flow. This affects the performance of this command, and you are recommended to review any long-running message flows.
If you have included a plug-in node or parser within a message flow on the broker, these are deleted by this command, and the relevant termination functions called. When message flows are restarted, the resources used by these nodes and parsers are re-accessed and reacquired. However, you are recommended to ensure that user-written plug-in nodes and parsers provide their own mechanism to reload persistent state and data dynamically, and do not rely on the use of this command |
Check your system's eventlog/system logs for any errors. |
|
| 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
|
|
|
|
