| Author |
Message
|
| karthik_ps |
 Posted: Thu Dec 19, 2013 1:00 am Post subject: EG become hang state |
 |
|
Apprentice
Joined: 10 Dec 2008
Posts: 43
|
Dear All,
In the Production server, We are using Message Broker version 8.0.0.2 and Message Queue version 7.0.3. Suddenly, An execution group under a broker become non operational without any notification. That means, message flows that are deployed under Execution groups, are not working. However, other execution groups message flows are working fine. If the Message flows interact with queue, ipprocs of the queue becomes zero. On checking status of broker, EGs and message flow, it shows up and running. When we try to stop a message flow or reload execution group, broker is not responding to any administrative commands. Once we restart the broker forcefully by killing the processes, duplicate engines are getting created. As of now, we don’t have any solution for duplicate engine though we have applied latest fix pack 8.0.0.2.
We have noted the below messages logged in the /var/adm/messages whenever this issue happens.
Dec 18 09:08:42 prd01 WebSphere Broker v8002[17070]: [ID 702911 user.error] (PRD1.ABC.BRK.default)[35]BIP2851E: The broker object '' of type 'Application' with uuid '' is in stopped state. The requested operation type 'Start' against an object type of 'Report' cannot be completed. : PRD1.ABC.BRK.7b7bc8aa-1d01-0000-0080-d701ce07905d: /build/slot1/S800_P/src/DataFlowEngine/ImbDeployedResourceGroup.cpp: 2572: ImbDeployedResourceGroup::startResource: Application: 7b7bc8aa-1d01-0000-0080-d701ce07905d
Dec 17 10:51:45 osiprd02 WebSphere Broker v8002[26619]: [ID 702911 user.error] (PRD2.BHL.BRK.PRD2.BHL.KLL.EXE)[35]BIP2851E: The broker object '' of type 'Application' with uuid '' is in stopped state. The requested operation type 'Start' against an object type of 'Report' cannot be completed. : PRD2.BHL.BRK.ef9ee63d-2701-0000-0080-cad9eaae214b: /build/slot1/S800_P/src/DataFlowEngine/ImbDeployedResourceGroup.cpp: 2572: ImbDeployedResourceGroup::startResource: Application: ef9ee63d-2701-0000-0080-cad9eaae214b
Please help. Thanks in advance.
Regards,
Karthik |
|
| Back to top |
|
 |
| McueMart |
| Posted: Thu Dec 19, 2013 2:35 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
The latest fixpack is 8.0.0.3 (not 8.0.0.2), you might want to try upgrading to this.
If it is a reproducible issue, you might want to try enabling User or Service trace on the EG (not ideal in production if its a performance critical application though). |
|
| Back to top |
|
|
| fastlearner |
| Posted: Fri Dec 20, 2013 10:56 pm Post subject: |
|
|
Newbie
Joined: 16 Oct 2012
Posts: 6
|
We are also facing the same issue on 8.0.0.2 - WMQ 7.5 on AIX. This seems to happen for some EG out of sudden. We also find abends occuring sometimes. My suggestion would be to raise a PMR.
We all jump to "upgrade to latest fix pack" so quickly without considering project constraints(cost ,time , downtime etc).
I'm really frustrated with WMB v8.0 , have already upgraded twice (7 - 8 - 8.0.0.2 ) and our production is no way near being as stable and dependable as 7.
I offer no solutions but I wish you good luck with the PMR. |
|
| Back to top |
|
|
| fastlearner |
| Posted: Fri Dec 20, 2013 11:12 pm Post subject: |
|
|
Newbie
Joined: 16 Oct 2012
Posts: 6
|
| Also IBM recommended that we set heap size for the EG to 1 GB which did not help either. |
|
| Back to top |
|
|
| karthik_ps |
| Posted: Sun Dec 22, 2013 12:37 am Post subject: |
|
|
Apprentice
Joined: 10 Dec 2008
Posts: 43
|
| Is there a way(workaround) to resolve this issue ( i.e., when duplicate engine is created ). IBM suggested way of killing process did not work out. (bipservice, bipbroker, biphttplistener, start listener scripts, all eg's ). |
|
| Back to top |
|
|
| Sovesky |
| Posted: Thu Dec 26, 2013 2:09 am Post subject: |
|
|
Novice
Joined: 30 Aug 2013
Posts: 17
|
| Curiously, all of a sudden I'm having the same issue on a DEV installation. It happened with a simple broker stop-start. |
|
| Back to top |
|
|
| sumit |
| Posted: Thu Dec 26, 2013 3:07 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
|
| Back to top |
|
|
| achocks |
| Posted: Sat Dec 20, 2014 4:48 pm Post subject: same issue with 8.0.0.4 |
|
|
Voyager
Joined: 28 Nov 2011
Posts: 82
|
| We also have the exact same problem in production with 8.0.0.4 version. Customers are frustrated with the unstablity. Anyone resolved this issue? Very interested to hear the solution. |
|
| Back to top |
|
|
|
|
