JR51910: INSTANCE MIGRATION FEATURE TO DEFER EXECUTION CONTEXT CHECKING DURING IN-FLIGHT MIGRATION FROM ONE SNAPSHOT TO SNAPSHOT
Direct links to fixes
Closed as program error.
When migrating instances certain difference between snapshots (ie. removed activities/events from design) may lead to errors during migration.
Inflight instance migration might complete successfully, but after the instances are migrated, you might see an exception that is similar to the following exception when you try to resume the instance: ?com.lombardisoftware.core.TeamWorksException: Attempt to access TWObject with classId TWClass.8c4bf039-0ec6-4ee9-b9af-d943e748701d that is not available rootContext=Snapshot.f7521b11-0122-40b6-bce3-8b89fea16c2a The error occurs because a TWObject(Business object) has been removed from the new snapshot. When the instance was migrated to the new snapshot, which is missing a business object, the migration logic does not check the underlying instance data to determine whether the two snapshots are compatible. Therefore, the migration successfully completes. However, you can no longer run the migrated instance on the new snapshot because of the error. Also, you can no longer migrate the instances back to the previous snapshot because the migration tries to load the execution context of the task to be migrated, which causes the same exception.
The fix is available for IBM BPM v220.127.116.11. With the fix applied, if you enable the ?defer-ec? property you can migrate the instances back to their original snapshots by not loading and updating the execution context during instance migration. With this property enabled, you can also re-create the missing objects in the new snapshot. When the missing items have been re-created in the new snapshot. you can migrate these instances again. Because the missing items have been re-added, you can run the instance. For defer-ec to work, you must add the following properties to the 100Custom.xml file: <server> <instance-migration merge="mergeChildren"> <thread-pool-size merge="replace">5</thread-pool-size> <migrate-tasks merge="replace">skip-closed</migrate-tasks> <defer-ec merge="replace">true</defer-ec> </instance-migration> </server> On Fix Central (http://www.ibm.com/support/fixcentral), search for JR51910: Select IBM Business Process Manager with your edition from the product selector, the installed version to the fix pack level, and your platform, and then click Continue. Select APAR or SPR, enter JR51910, and click Continue. When you download fix packages, ensure that you also download the readme file for each fix. Review each readme file for additional installation instructions and information about the fix.
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels