Fixes are available
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
Example Scenario: 1) Submit BonusPayout.partitioned.collector with 1000 records 2) Once partitions are started, gracefully stop the secondary server 3) Verify the status of the job is Started/Dispatched 4) Restart the secondary executor 5) Notice the status of the job is Started/Dispatched on all servers 6) Issue a stop to the job 7) Verify the job state goes Stopped 8) Restart the job 9) Notice the job runs, but fails with an exit status of 1010 Step 9 shows that the rollback did not occur properly since the exitStatus value does not match the number of records of the submitted job.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server Liberty Profile- Batch * **************************************************************** * PROBLEM DESCRIPTION: The exitStatus after the restart of an * * executor is not properly being rolled * * back to the correct value. * **************************************************************** * RECOMMENDATION: * **************************************************************** Example Scenario: 1) Submit BonusPayout.partitioned.collector with 1000 records 2) Once partitions are started, gracefully stop the secondary server 3) Verify the status of the job is Started/Dispatched 4) Restart the secondary executor 5) Notice the status of the job is Started/Dispatched on all servers 6) Issue a stop to the job 7) Verify the job state goes Stopped 8) Restart the job 9) Notice the job runs, but fails with an exit status of 1010 Step 9 shows that the rollback did not occur properly since the exitStatus value does not match the number of records of the submitted job.
Problem conclusion
The previous user data object is now persisted whenever a new value is used to update it. When a transaction fails to commit and throws an error the previous user data object that was persisted will replace the current object to allow for the rollback to perform properly. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.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
PI58049
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-02-25
Closed date
2016-02-25
Last modified date
2016-02-25
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
WAS LIBERTY COR
Fixed component ID
5725L2900
Applicable component levels
R855 PSY
UP
Document Information
Modified date:
28 April 2022