| Author |
Message
|
| vsethi007 |
 Posted: Mon Jul 14, 2008 3:21 am Post subject: Broker Problem |
 |
|
Novice
Joined: 17 Apr 2008
Posts: 19
|
Hi
I am facing a strange problem , while deploying any flow into Execution Group.
Any flow deployed in Execution group get deployed in STOP mode and then I need to start it, remove it and then deploy again.
This problem occurs specially in flows which has database interaction.
Any body, please suggest how to rectify that..and what causes that problem to occur. |
|
| Back to top |
|
 |
| srina |
| Posted: Mon Jul 14, 2008 5:30 am Post subject: |
|
|
Novice
Joined: 06 Jul 2008
Posts: 10
|
| before u trying to Re Deploy right click cancel the deployment and refresh it and now u can redeploy it works |
|
| Back to top |
|
|
| vsethi007 |
| Posted: Mon Jul 14, 2008 10:38 pm Post subject: |
|
|
Novice
Joined: 17 Apr 2008
Posts: 19
|
One thing to add in it,
when I try starting the flow, I get these Errors which I can see in eventlog of toolkit.
BIP2270W: Request to start message flow '9245a021-1b01-0000-0080-a01ca4e5db59': message flow does not exist.
The message broker received an operational control message containing an instruction to start the message flow '9245a021-1b01-0000-0080-a01ca4e5db59', but this message flow does not exist.
Ensure that the message flow, and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
BIP4041E: Execution group 'EG' received an invalid configuration message. See the following messages for details of the error.
The message broker received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).
Check the relevant message flow and message set definitions, check that all necessary user-defined extensions are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues.
BIP2087E: Broker BROKER_C was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
The internal configuration message failed to be processed, use the messages following this message to determine the reasons for the failure.
I tried cancelling the depoyment and refreshing too.but it didn't helped |
|
| Back to top |
|
|
| sami.stormrage |
| Posted: Tue Jul 15, 2008 8:29 am Post subject: |
|
|
Disciple
Joined: 25 Jun 2008
Posts: 186
Location: Bangalore/Singapore
|
what is the version of MB that ur running.. Is it a case of errornous message set? can you be 100% sure that its not a problem with the message set .. and then procede to see the SYSTEM.BORKER Q's if there are messages piling up on them?
_________________
*forgetting everything  * |
|
| Back to top |
|
|
| chrisc |
| Posted: Tue Jul 15, 2008 5:54 pm Post subject: |
|
|
Voyager
Joined: 19 Mar 2006
Posts: 77
|
It sounds like you might be trying to deploy a v6 message flow to a v5 Broker, or perhaps 6.1 to a 6.0 Broker...
The message about trying to start a flow that doesn't exist though is definitely weird. It's almost as though your Config Mgr has become out of sync with the contents of the Broker itself somehow.
Alternatively, your execution groups may have become seriously screwy (it happens sometimes). If you're sure you've got the correct versions of everything, try right clicking on the execution group and selecting "remove all deployed children". This sometimes flushes out bizarre phantom flows and other problems.
And there's always that famous IT standby: restart everything (config manager, broker, OS...) |
|
| Back to top |
|
|
| vsethi007 |
| Posted: Wed Jul 16, 2008 1:38 am Post subject: |
|
|
Novice
Joined: 17 Apr 2008
Posts: 19
|
I am using Broker Version 6.0.0.3 , and there is no mesage set involved only message flows...
moreover I tried deleting the execution group creaed a new one then restarted the Broker, execution group and everthing..but still the problem persists..
one thing I noticed is this exceution group is eating a lot of memory on server |
|
| Back to top |
|
|
| AkankshA |
| Posted: Wed Jul 16, 2008 1:46 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
| vsethi007 wrote: |
moreover I tried deleting the execution group creaed a new one then restarted the Broker, execution group and everthing..but still the problem persists..
one thing I noticed is this exceution group is eating a lot of memory on server |
indicates some curroption to me..
can you try one thing...
stop off all the current components and creata fresh set of configMgr / broker / exec grp etc....
if exec grp still eats up a lot of memory then we might be in trouble..
_________________
Cheers |
|
| Back to top |
|
|
|
|
