Fixes are available
APAR status
Closed as program error.
Error description
The process of stopping a snapshot/app remains stuck. After applying JR43190 clicking "Stop" for a given snapshot, the process admin console displays stopped but after restarting the server it shows as "Stopping" for the snapshot endlessly.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: ALL * **************************************************************** * PROBLEM DESCRIPTION: The process of stopping a * * snapshot/app remains stuck. * * After applying JR43190 clicking * * "Stop" for a given snapshot, the * * process admin console displays * * stopped but after restarting the * * server it shows as "Stopping" for the * * snapshot endlessly. * **************************************************************** * RECOMMENDATION: * **************************************************************** The process of stopping a snapshot/app remains stuck. After applying JR43190 clicking "Stop" for a given snapshot, the process admin console displays stopped but after restarting the server it shows as "Stopping" for the snapshot endlessly.
Problem conclusion
Applying JR44282 fixes the problem. The Install/Dependency information is available in the readme.txt on FixCentral. When the user goes to the download files page in FixCentral the readme will be available with the fix package as a seperate download. Note: After applying this fix, the Process Applications that were showing "Stopping" status will show a blank status and the applications will need to be stopped again using the stop button. After a server restart it causes the BLA to automatically start back and hence the application that was stopped will return to stopping state. For the snapshots that were showing the 'stopping' status (problematic snapshots), after applying the fix and after starting the server: - The stopped applications will appear without current state, (blank state in front of them). that means its an internal representation of the "inactive" state and hence no state is shown. - such applications should be stopped again using the stop button before activating them. WAS forces the start of the enterprise applications/BLAs on server start. So in the fix we compensate from the above WAS behavior and recover the state to inactive.
Temporary fix
Comments
APAR Information
APAR number
JR44282
Reported component name
BPM EXPRESS
Reported component ID
5725C9600
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-10-04
Closed date
2012-10-24
Last modified date
2012-11-29
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
BPM EXPRESS
Fixed component ID
5725C9600
Applicable component levels
R750 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTBX","label":"IBM Business Process Manager Express"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
29 November 2012