Direct link to fix
APAR status
Closed as program error.
Error description
If one of the System toolkits has multiple snapshot versions, running the BPMUpdateSystemApp might fail to import that toolkit. The following exception is logged in the BPMUpdateSystemApp.log file: [3/15/19 16:56:31:003 CDT] 00000001 ImportFileHel E CWLLG2015E: An unexpected runtime exception occurred. See exception for more details. Error: Error updating branch end dating of 17 IDs: updated 16 rows, not 17. com.lombardisoftware.core.TeamWorksRuntimeException: Error updating branch end dating of 17 IDs: updated 16 rows, not 17 at com.lombardisoftware.server.ejb.persistence.versioning.MutableSn apshotContextImpl.endDatePOVersions(MutableSnapshotContextImpl.j ava:556) at com.lombardisoftware.server.ejb.persistence.versioning.MutableSn apshotContextImpl.delete(MutableSnapshotContextImpl.java:357) at com.lombardisoftware.server.ejb.persistence.versioning.MutableSn apshotContextImpl.delete(MutableSnapshotContextImpl.java:328) at com.lombardisoftware.core.deployment.ImportHelper$3.run(ImportHe lper.java:796) at com.lombardisoftware.core.TeamWorksRunnable.call(TeamWorksRunnab le.java:7) at com.lombardisoftware.core.TeamWorksRunnable.call(TeamWorksRunnab le.java:5) at com.lombardisoftware.server.ejb.persistence.versioning.BranchMan ager$2.withWriteAccess(BranchManager.java:344) at com.lombardisoftware.server.ejb.persistence.versioning.BranchCon textImpl.writeAccessWithDBLock(BranchContextImpl.java:590) at com.lombardisoftware.server.ejb.persistence.versioning.BranchCon textImpl$MultiPhaseWriteAccessImpl.execute(BranchContextImpl.jav a:268) at com.lombardisoftware.server.ejb.persistence.versioning.BranchMan ager$TransactionScope.execute(BranchManager.java:996) at com.lombardisoftware.server.ejb.persistence.versioning.BranchMan ager.writeAccess(BranchManager.java:370) at com.lombardisoftware.server.ejb.persistence.versioning.BranchMan ager.createNewSnapshot(BranchManager.java:695)
Local fix
Restart the server and manually run the BPMUpdateSystemApp command to import the System toolkit.
Problem summary
When a System toolkit with multiple snapshot versions gets updated by running the BPMUpdateSystemApp command, the internal branch cache in the Branch Manager might gets corrupted, which causes the BPMUpdateSystemApp command to fail. However, because this is a internal cache, no corruption occurs on the database side. PRODUCT AFFECTED IBM Business Automation Workflow
Problem conclusion
A fix that ensures the internal cache isn't corrupted when the BPMUpdateSystemApp command runs is included in IBM Business Automation Workflow V18.0.0.1.
Temporary fix
Comments
APAR Information
APAR number
JR61097
Reported component name
BPM
Reported component ID
5737A5700
Reported release
I00
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-05-15
Closed date
2019-05-22
Last modified date
2019-05-22
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
BUS AUTO WORKFL
Fixed component ID
5737H4100
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
22 May 2019