IBM Support

JR53189: INSTANCE MIGRATION FAILURE DUE TO BPD CANNOT BE FOUND ERROR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • When migrating process instances, if the instance
    being migrated is currently executing on a BPD that
    does not exist in the target snapshot, runtime and migration
    errors will occur.
    The migration to the target snapshot will succeed without any
    errors.
    However, when trying to resume the instance, a runtime error
    will occur.
     Also, attempting to migrate the instance back to the old
    snapshot will fail as well with the following exception in the
    logs:
    
    RuntimeServic E SERVER_MIGRATION_FAILURE when migrating BPD
    with instance ID = BPDInstance.1097 from snapshot
    Snapshot.bf11bb48-e195-40de-964a-c602940909ec to target
    snapshot Snapshot.f2e19ff9-1717-4e2f-9afa-008197488184
    
    com.lombardisoftware.core.TeamWorksException: Business Process
    Diagram with ID BPD.14f4494d-930a-4d36-871a-381138da076d not
    found.
    
    The exception during resuming the instance is expected since
    runtime cannot find the BPD model to resume from.
    However, the process instance should be able to migrate back to
    the old snapshot so the process instance may continue and
    complete.
    

Local fix

Problem summary

  • ERROR DESCRIPTION -
    When migrating instances from one snapshot to another, the
    migration fails due to a missing service or BPD in the source
    snapshot.
    The following error may be seen when attempting to migrate:
    CWLLG0234E: An attempt to get a process instance
    (id=100,115,502) failed because of an unexpected exception.
    Error: Service with ID
    TWProcess.d908445e-2f52-4874-8a37-5ddc5a9fdf1b not found.
    
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM) Advanced
    IBM BPM Standard
    IBM BPM Express
    
    LOCAL FIX -
    None
    
    
    PROBLEM SUMMARY
    Instance migration will fail if you try to migrate an instance
    which has a service or BPD that does not exist in the source
    snapshot.  To get into this case scenario, the initial migration
    of instances to the new snapshot will succeed even when the
    target snapshot is missing some artifacts.  However, when the
    user tries to migrate these instance back to the initial
    snapshot, the migration fails as the current snapshot's model
    does not have the missing artifacts.
    In this case, the instances are stuck running on the current
    snapshot and may encounter runtime failures due to the missing
    artifacts.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR53189

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    801

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-04-24

  • Closed date

    2015-07-07

  • Last modified date

    2015-07-07

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

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

Fix information

Applicable component levels

  • R856 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTDH","label":"IBM Business Process Manager Standard"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
07 July 2015