JR48788: NULLPOINTEREXCEPTION WHEN MIGRATING A PROCESS INSTANCE RUNNING A GENERALIZED FLOW

Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products
Download Version 8.0.1 Fix Pack 3 for the IBM Business Process Manager products

APAR status

• Closed as program error.

Error description

• When a process instance that is currently navigating a
  single-threaded
  region in a generalized flow, it can happen that
  the migration aborts with the following root cause:
  
               java.lang.NullPointerException
   at
  com.ibm.bpe.engine.migration.MigrationHandler.addSingleMessage(M
  igration
  Handler.java:794)
   at
  com.ibm.bpe.engine.migration.MigrationHandler.determineNavigatio
  nFront(M
  igrationHandler.java:427)
   at
  com.ibm.bpe.engine.migration.MigrationHandler.migrate(MigrationH
  andler.j
  ava:197)
   at
  com.ibm.bpe.engine.BpelEngineCore.migrate(BpelEngineCore.java:10
  430)
   at com.ibm.bpe.engine.BpelEngine.migrate(BpelEngine.java:8625)
   at
  com.ibm.bpe.framework.BusinessProcessServiceImpl.migrate(Busines
  sProcess
  ServiceImpl.java:27236)
  
  
  Normally, during navigation of a process, it is required that
  all
  activity instances of the so called navigation front are
  persisted to
  the database.
  The navigation front is the set of activities that have been
  navigated
  at last inside a navigation transaction.
  In some situation it happens that an activity instance that
  belongs to
  the navigation front is not persisted. The activity instance is
  not
  found
  during instance migration and as a result a NullPointerException
  is
  thrown.
  

Local fix

• n/a
  

Problem summary

• NullPointerException when migrating a process instance running a
  generalized flow.
  
  PROBLEM DETAILED DESCRIPTION:
  When a process instance, that is currently navigating a
  single-threaded region in a generalized flow, is migrated, it
  can happen that the migration aborts with the following root
  cause:
  
         java.lang.NullPointerException
   at com.ibm.bpe.engine.migration.MigrationHandler.
     addSingleMessage(MigrationHandler.java:794)
   at com.ibm.bpe.engine.migration.MigrationHandler.
     determineNavigationFront(MigrationHandler.java:427)
   at com.ibm.bpe.engine.migration.MigrationHandler.
     migrate(MigrationHandler.java:197)
   at com.ibm.bpe.engine.BpelEngineCore.migrate
     (BpelEngineCore.java:10430)
   at com.ibm.bpe.engine.BpelEngine.migrate
     (BpelEngine.java:8625)
   at com.ibm.bpe.framework.BusinessProcessServiceImpl.
     migrate(BusinessProcessServiceImpl.java:27236)
  
  Normally, during navigation of a process, it is required that
  all activity instances of the so called navigation front are
  persisted to the database.  The navigation front is the set of
  activities that have been navigated at last inside a navigation
  transaction.
  In some situation it happens that an activity instance that
  belongs to the navigation front is not persisted. The activity
  instance is not found during instance migration and as a result
  a NullPointerException is thrown.
  

Problem conclusion

• With this fix it is ensured that also activity instances inside
  generalized flows, that make up the navigation front are
  persisted to the database.
  It is important to understand that this fix need already be
  installed before the migration takes place.  Although the
  exception happens at migration time, the cause of this issue is
  fixed in the normal navigation of processes.
  
  FIX AVAILABILITY:
  Fix is targetted for inclusion in next fixpack for BPM V7.5.1,
  BPM 8.0.1
  

Temporary fix

Comments

APAR Information

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

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

  IV53217

Fix information

• Fixed component name

  BPM ADVANCED

• Fixed component ID

  5725C9400

Applicable component levels

• R751 PSN

     UP

• R801 PSN

     UP