PM01123: AFTER STOPPING A BPC APPLICATION THAT HAS A RUNNING PROCESS INSTANCE, THE APPLICATION GETS IN AN UNSTOPPABLE STATE.

Fixes are available

APAR status

Closed as program error.

Error description

The CompostionUnitMgr expects that when a CompositionUnit is
asked to stop, that it will indeed stop.  Because the J2EE type
CompositionUnit does not stop because of the running process,
the CompositionUnit and Application states get out of sync.
This prevents the stopping of the application at a later
time.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All IBM WebSphere Application Server V7.0   *
*                  users who stop Business Process             *
*                  Choreographer (BPC) applications with       *
*                  running process instances.                  *
****************************************************************
* PROBLEM DESCRIPTION: After attempting to stop a BPC          *
*                      application with running process        *
*                      instances, you cannot stop the          *
*                      application after the instances have    *
*                      completed.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The WebSphere Application Server does not expect that a
Composition Unit (CU) will not stop when requested. Since the
BPC application for the Composition Unit does not stop, the
application and CU states get out of sync and further actions
on the application will not complete successfully.

Problem conclusion

The Composition Unit was changed to allow the BPC application
to signal back that it was not stopped allowing the
Composition Unit to not stop. This leaves the application and
Composition Unit states in sync.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.9.  Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM01123
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-12
Closed date
2009-11-17
Last modified date
2009-11-17

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM01123: AFTER STOPPING A BPC APPLICATION THAT HAS A RUNNING PROCESS INSTANCE, THE APPLICATION GETS IN AN UNSTOPPABLE STATE.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?