| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| can not start egroup |
« View previous topic :: View next topic » |
| Author |
Message
|
| wilsonho3 |
 Posted: Wed May 19, 2010 11:04 pm Post subject: can not start egroup |
 |
|
Voyager
Joined: 20 Nov 2001
Posts: 98
Location: Hong Kong
|
hi,
I have an env. on AIX, some of the egroup can not start for so-called
create VM issue. the log as following: the fail egroup is call "debug" and
thmas
May 20 14:42:57 esbaixdev01 user:info WebSphere Broker v6003[819260]: (EBBKD1.Debug)[1]BIP7064S: Failed to create Java VM -4. : EBBKD1.f51a6f78-1101-0000-0080-d7c6e1f40ac0: /build/S600_P/src/JNI/ImbJVM.cpp: 617: ImbJVM::createJVM: :
May 20 14:42:57 esbaixdev01 user:info WebSphere Broker v6003[819260]: (EBBKD1.Debug)[1]BIP2204I: Execution group using process '819260' thread '1' stopped. : EBBKD1.f51a6f78-1101-0000-0080-d7c6e1f40ac0: /build/S600_P/src/DataFlowEngine/ImbMain.cpp: 890: main: :
May 20 14:42:57 esbaixdev01 user:warn|warning WebSphere Broker v6003[778424]: (EBBKD1)[1543]BIP2060W: The broker has detected that the Execution Group Debug, process ID 819260, has shutdown. : EBBKD1.agent: /build/S600_P/src/AdminAgent/ImbAdminAgent.cpp: 4139: ImbAdminAgent::startAndMonitorADataFlowEngine: :
May 20 14:42:57 esbaixdev01 user:err|error WebSphere Broker v6003[860398]: (EBBKD1.Thomas)[1]BIP2203E: An execution group has encountered a problem whilst starting. : EBBKD1.080a5b39-1e01-0000-0080-e0f7d2669fbc: /build/S600_P/src/DataFlowEngine/ImbMain.cpp: 833: main: :
May 20 14:42:57 esbaixdev01 user:info WebSphere Broker v6003[860398]: (EBBKD1.Thomas)[1]BIP7064S: Failed to create Java VM -4. : EBBKD1.080a5b39-1e01-0000-0080-e0f7d2669fbc: /build/S600_P/src/JNI/ImbJVM.cpp: 617: ImbJVM::createJVM: :
pls advise what is the issue. ths
wil |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Thu May 20, 2010 12:13 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
|
| Back to top |
|
|
| wilsonho3 |
| Posted: Sun May 23, 2010 11:25 pm Post subject: |
|
|
Voyager
Joined: 20 Nov 2001
Posts: 98
Location: Hong Kong
|
hi, mqmatt
Increase heap size with error :
esbaixdev01:/home/wbrkadm> mqsichangeproperties EBBKD1 -e Debug -o ComIbmJVMManager -n jvmMaxHeapSize -v 16777216
BIP2087E: Broker EBBKD1 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.
BIP2066E: Broker EBBKD1 (UUID 6f87da55-0f01-0000-0080-8e4ae84e0164) was unable to retrieve an internal configuration response message for execution group 'Debug' within the 360 second Configuration Timeout.
The execution group did not respond within the Configuration Timeout period. A negative response is returned to the Configuration Manager for this execution group. The Configuration Timeout is the maximum length of time that an execution group is allowed to apply a deployed configuration change. By default the Configuration Timeout period is 300 seconds. You can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationTimeout. This will not resolve any underlying problem with the deployed message, but can be used to reduce the response turnaround time or increase it to allow for large and complex deployments.
Investigate why the execution group was unable to respond before being timed out. Use the system log messages to determine if there is a problem with the execution group. You should check that your system is not running short of resources, for example, you may need to increase the WebSphere log size. Reducing the complexity of the deploy by reducing the number of execution groups may also help to alleviate this problem. Correct the problem and redeploy the broker's configuration from the Message Brokers Toolkit, mqsideploy command or Config Manager Proxy. If there are no other failure diagnostics then you should consider increasing the Configuration Timeout, increase this value in units of 300 until this message no longer occurs. Contact your IBM support center if you are unable to resolve the problem.
BIP8036E: Negative response received.
This command sends an internal configuration message to the broker, the response received indicated that the internal configuration message was unsuccessful.
Check that the WebSphere MQ transport is available. Check the system log for further information.
pls advise how to save the problem e-group without deletion
wilson |
|
| Back to top |
|
|
| li.simon |
| Posted: Fri Jul 09, 2010 1:43 am Post subject: |
|
|
Newbie
Joined: 08 Jul 2010
Posts: 1
|
Your problem might relates to DataFlowEngine runs out of allocated address space.
You can resolve the problem in the following ways -
1. Create a 64-bit Execution Group and delete the current 32-bit Execution Group.
OR
2. Assign 5 memory segments or 1.24 GB to the DataFlowEngine by exporting the environment variable - LDR_CNTRL=MAXDATA in the following way -
export LDR_CNTRL=MAXDATA=0x50000000
Restart the broker
If the problem persists, then increase the number of memory segments for the DataFlowEngine to 0x60000000. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jul 09, 2010 2:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I'd merely make sure that the EG is not stuck in a loop when you attempt to change the jvmMaxHeap ... so that it responds to the configuration command in a timely fashion...
Perhaps by creating a *NEW* EG, setting the max heap on that, and then deploying all the flows in the old EG to the new one, and then removing the old one.
LOOK MA, NO DOWNTIME. |
|
| 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
|
|
|
|
