IV61624: BPEL PROCESS INSTANCE MIGRATION - ASSERTION AT DEPLOY/START

APAR status

• Closed as program error.

Error description

• Scenario: For BPE process instance version migration a new
  version of
  the process template has to be created in a new application.
  Additionally definitions must be created for the migration from
  the
  source template version to the target template version.
  Afterwards the new app (containing the new version) is deployed
  to the
  server. During startup the following assertion is seen in the
  logs:
  
  com.ibm.bpe.util.ProcessAssertionError: Assertion violation
  !(containmentLevelPast == ContainmentLevel.NOT_CONTAINED) in
  method >>
  com.ibm.bpe.deployment.migration.WaveFrontChangeGroupRelationshi
  pCalcula
  tor.determineRelationship(WaveFrontChangeGroupRelationshipCalcul
  ator.jav
  a:272) <<
   at com.ibm.bpe.util.Assert.assertion(Assert.java:70)
   at
  com.ibm.bpe.deployment.migration.WaveFrontChangeGroupRelationshi
  pCalcula
  tor.determineRelationship(WaveFrontChangeGroupRelationshipCalcul
  ator.jav
  a:272)
   at
  com.ibm.bpe.deployment.migration.WaveFrontChangeGroupRelationshi
  pCalcula
  tor.determineRelationship(WaveFrontChangeGroupRelationshipCalcul
  ator.jav
  a:199)
   at
  com.ibm.bpe.deployment.migration.ChangeGroupCalculatorImpl.deter
  mineChan
  geGroups(ChangeGroupCalculatorImpl.java:119)
   at
  com.ibm.bpe.deployment.bpel.importer.impl.ImporterImpl$1.run(Imp
  orterImp
  l.java:440)
  

Local fix

• N/A
  

Problem summary

• A new version of a BPEL process has been created. To enable the
  migration of any existing process instances to the new version,
  a process migration specification has been defined. During
  deployment of the application with the new version of the BPEL
  process the application fails to start and the following
  assertoin error is reported in the logs:
  
  com.ibm.bpe.util.ProcessAssertionError: Assertion violation
  !(containmentLevelPast == ContainmentLevel.NOT_CONTAINED) in
  method >>
  com.ibm.bpe.deployment.migration.WaveFrontChangeGroupRelationshi
  pCalculator.determineRelationship(WaveFrontChangeGroupRelationsh
  ipCalculator.java:272)
  
  The assertion violation may appear if an invoke or scope
  activity with an attached fault or event handler is nested
  within a generic flow activity and changes are mode in the
  logic of the handler. It happens because the code does not
  recognize that the logic of the handler is nested within a
  generic flow activity.
  

Problem conclusion

• The problem has been fixed by changing the code so that it now
  recognizes that the logic of the handler is nested within a
  generic flow activity.
  

Temporary fix

Comments

APAR Information

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

  JR46404

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

Fix information

• Fixed component name

  BUS PRC CHOREOG

• Fixed component ID

  5655FLW11

Applicable component levels