| Author |
Message
|
| cvag |
 Posted: Tue Jan 26, 2010 10:52 am Post subject: Message Flow is not starting |
 |
|
Centurion
Joined: 17 Mar 2008
Posts: 127
|
Hi
I have developed simple flow and deployed on to the broker6.1 . I tested the flow without debug mode, it works fine.
And the execution group is assigned with port number
C:\Program Files\IBM\MQSI\6.1>mqsilist WBRK61_DEFAULT_BROKER
BIP8130I: Execution Group: default - 5008
But the strange thing i cound not able to find it..
I assigned the jvm port to test the message flow with debug mode, but when i restarted the broker the message flow is not starting and moreover the port of Execution Group is assigning to Zero automatically.
C:\Program Files\IBM\MQSI\6.1>mqsilist WBRK61_DEFAULT_BROKER
BIP8130I: Execution Group: default - 0
Error Message in Event Viewer:
( WBRK61_DEFAULT_BROKER ) The broker has detected that the Execution Group 'default', process ID 1036, has shutdown.
An Execution Group has shutdown. A new instance of the execution group will be started in approximately 0 seconds.
Investigate any prior system log messages for possible problems. Contact your IBM support center if you are unable to determine the cause of the shutdown.
----------------
( WBRK61_DEFAULT_BROKER.default ) Execution group (32) started: process '1036'; thread '3580'; additional information: brokerName ''WBRK61_DEFAULT_BROKER'' (operation mode ''enterprise''); executionGroupUUID ''cf0fc36b-2601-0000-0080-929cfb1ff972''; executionGroupLabel ''default''; defaultExecutionGroup 'true'; queueManagerName ''WBRK61_DEFAULT_QUEUE_MANAGER''; trusted 'false'; dataSourceName ''DEFBKD61''; userId ''Gunipe''; migrationNeeded 'false'; brokerUUID ''e70bc36b-2601-0000-0080-929cfb1ff972''; filePath ''C:\Program Files\IBM\MQSI\6.1''; workPath ''C:\Documents and Settings\All Users\Application Data\IBM\MQSI''; ICU Converter Path ''''.
The execution group has started using process '1036' and thread '3580' and will now start to process messages.
No user action required.
----------------------------
Could anybody pls give the root cause for this failure and the suggestion for solving  .
Thanks in Advance. |
|
| Back to top |
|
 |
| SANTYP |
| Posted: Tue Jan 26, 2010 7:05 pm Post subject: |
|
|
Centurion
Joined: 27 Mar 2007
Posts: 142
|
| Have u restarted the broker after settingup the jvm port..? |
|
| Back to top |
|
|
| cvag |
| Posted: Tue Jan 26, 2010 8:05 pm Post subject: |
|
|
Centurion
Joined: 17 Mar 2008
Posts: 127
|
Yes thats what i mentioned in the above
"But the strange thing i cound not able to find it..
I assigned the jvm port to test the message flow with debug mode, but when i restarted the broker the message flow is not starting and moreover the port of Execution Group is assigning to Zero automatically.
C:\Program Files\IBM\MQSI\6.1>mqsilist WBRK61_DEFAULT_BROKER
BIP8130I: Execution Group: default - 0 "
Any suggestions pls.. |
|
| Back to top |
|
|
| cvag |
| Posted: Tue Jan 26, 2010 8:11 pm Post subject: |
|
|
Centurion
Joined: 17 Mar 2008
Posts: 127
|
Sorry for my mistake, not the port number .. process Id is changing to 0
When i issue the command mqsilist <Brokername>
Any ideas pls.. |
|
| Back to top |
|
|
| moonwalker |
| Posted: Tue Jan 26, 2010 10:47 pm Post subject: |
|
|
Apprentice
Joined: 02 Jun 2009
Posts: 42
|
I thing there should be no problem because the event log clearly specifies as no user action is required.
A new process is being started for execution group as a result of the broker restart. |
|
| Back to top |
|
|
| cvag |
| Posted: Tue Jan 26, 2010 11:25 pm Post subject: |
|
|
Centurion
Joined: 17 Mar 2008
Posts: 127
|
Yes, this seems peculiar, the process id is vanishing and assigning the value to zeo after enabling jvm debug port and restarting the broker.
And moreover the process id is ending and starting another process id for execution group. This is not understandable.
Please post any suggestions to resolve this. Tried with many installations. installing java and checked the registry the value of execution group process id. (Process id is 0 after jvm debug port and restarting the broker )
Please help |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Jan 27, 2010 10:08 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
A few suggestions off the top of my head:
1) Make sure the port is not in use
2) Check the syslog for real errors
3) Apply v6.1.0.5 fixpack.
4) Grab system trace and raise a PMR. |
|
| Back to top |
|
|
|
|
