| Author |
Message
|
| madi |
 Posted: Wed Jun 07, 2006 7:40 am Post subject: wbi 6.0 broker error |
 |
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
Hi all
I had wbi 6.0 working fine until now
i get a alert box saying
| Quote: |
| The application closed the program 'DataFlowEngine.exe.' unexpectedly |
when i press OK it repeats again after a few seconds....... i look at the task manager list of processes and see that DB2 is taking 550 MB of RAM and the DataFlowEngine is being restarted everytime I press OK and I get thiz error again
then i stopped the broker and looked for errors in the application log and this is what i found
| Quote: |
( WBI6_BROK ) Execution Group 'default' failed to return an internal configuration 'Start' message response within a 60 second time period.
The internal configuration message response could not be retrieved. The Execution Group therefore failed to move to the state described by the internal configuration message.
Investigate why the Execution Group internal configuration message response was not returned within the allowed time period by reviewing messages issued to the system log. Additionally, you can increase (or decrease) the timeout by using the mqsichangebroker option, |
what does this mean and is there a fix for this without having to delete and create another broker??
i deployed successfully to the exec group about 1 week back
the only thing i changed is
mqsichangebroker -l /lil/path
do u think thats a problem??
--madi |
|
| Back to top |
|
 |
| wschutz |
| Posted: Wed Jun 07, 2006 8:15 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
the only thing i changed is
mqsichangebroker -l /lil/path
do u think thats a problem?? |
so you made that change and then immediately after the broker dataflow engine started having this problem?
Are you on windows? Why did you specify a unix style path?
_________________
-wayne |
|
| Back to top |
|
|
| madi |
| Posted: Wed Jun 07, 2006 9:04 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
| wschutz wrote: |
Are you on windows? Why did you specify a unix style path? |
yes im in windows ........... that was just an example path ...... i did specify a valid path where i had the jar files
now i am not able to connect to the config mgr from the tool kit!!
--madi |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 07, 2006 9:08 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Stop everything.
Start the configmgr.
Look at the Event Viewer to see what it says.
If it says that configmgr failed to start, troubleshoot that.
If it says that it is successful, start the Toolkit and see if you can connect.
If you can't connect, troubleshoot why.
Start the broker.
Look at Event Viewer to see what it says.
If it says that broker failed to start, troubleshoot what it says.
If it says that broker started, but that an EG failed to start, troubleshoot that.
If it starts, verify that configuration manager reports that broker started.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| madi |
| Posted: Wed Jun 07, 2006 9:18 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
| Quote: |
Stop everything.
Start the configmgr.
Look at the Event Viewer to see what it says.
If it says that configmgr failed to start, troubleshoot that.
If it says that it is successful, start the Toolkit and see if you can connect.
If you can't connect, troubleshoot why. |
so far everything went fine and am able to conenct to the config mgr after the restart
| Quote: |
Start the broker.
Look at Event Viewer to see what it says.
If it says that broker failed to start, troubleshoot what it says. |
no errors in the log saying anything about broker start
so now the whole thing happens again
db2 taking up a lot of RAM and then the alert saying
| Quote: |
Runtime Error!
Program: c:\...\...\6.0\bin\DataFlowEngine.exe
The application has requested to terminate it in an unsual way. |
now i have this in the application log
| Quote: |
( WBI6_BROK ) Execution Group 'default' failed to return an internal configuration 'Start' message response within a 60 second time period.
The internal configuration message response could not be retrieved. The Execution Group therefore failed to move to the state described by the internal configuration message.
Investigate why the Execution Group internal configuration message response was not returned within the allowed time period by reviewing messages issued to the system log. Additionally, you can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationDelayTimeout. This will not resolve any underlying problem with a deployed configuration message, but can be used to reduce the response turnaround time or allow for large and complex deployments. Resolve any problems described in the system log. This 'internal configuration' operation will be retried automatically, if you continue to see this message you should investigate the reason for the Execution Groups failure to respond. |
so this is what is happening
--madi |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jun 07, 2006 9:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That's the first and only entry in the Application Log? You don't see anything else after the broker starts?
Can you post every entry that shows up after broker starts?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| madi |
| Posted: Wed Jun 07, 2006 12:00 pm Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
| Quote: |
( WBI6_BROK ) The WebSphere Business Integration Message Brokers service has started, process ID 3808.
The WebSphere Business Integration Message Brokers service executable has been started.
No user action required. |
| Quote: |
( WBI6_BROK.default ) Execution Group started: process '696'; thread '2892'; additional information: brokerName 'WBI6_BROK'; executionGroupUUID '7b87148c-0b01-0000-0080-d9df00478aeb'; executionGroupLabel 'default'; defaultExecutionGroup 'true'; queueManagerName 'WBI6_CONFIG_QM'; trusted 'false'; dataSourceName 'WBI6BROK'; userId 'a025969'; migrationNeeded 'false'; brokerUUID '5d87148c-0b01-0000-0080-d9df00478aeb'; filePath 'C:/Program Files/IBM/WebSphere Business Integration Message Brokers'; workPath 'C:/Program Files/IBM/WebSphere Business Integration Message Brokers'.
The execution Group has started using process '696' and thread '2892' and will now start processing messages.
No user action required. |
| Quote: |
( WBI6_BROK.default ) Failure to locate Java class com.tgt.wbimb.enterprise.mq.JMQGetNode
The Java class com.tgt.wbimb.enterprise.mq.JMQGetNode could not be found by the Java API framework.
This is an internal error. Contact your IBM support center. |
| Quote: |
( WBI6_BROK.default ) Database record associated with message flow '7bfc5e95-0b01-0000-0080-e172d4b2e9ca' is not valid.
The message broker found a database record associated with the persistent state of message flow '7bfc5e95-0b01-0000-0080-e172d4b2e9ca' to be invalid. The active broker state may not be as expected.
See the following message or messages for details of the error. Attempt to correct the error or errors by redeploying the complete broker configuration from the Message Brokers Toolkit. If the problem persists, contact your IBM support center. |
| Quote: |
( WBI6_BROK.default ) LIL not found for message flow node type 'ComIbmMQGetNode' in message flow 'Test_Flow1'.
The message broker received an instruction to create a message flow node of type 'ComIbmMQGetNode', in message flow 'Test_Flow1'. The broker does not have the capability to create nodes of this type because an implementation library for this node type was not found in the LIL path.
Ensure that the LIL path is correct and contains all the necessary node implementation libraries, including those supplied by IBM. Then 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. |
i can see these errors this time |
|
| Back to top |
|
|
|
|
