JR63248: The bootstrapProcessServerData command for Business Automation Workflow(BAW) 20.0.0.2 fails with java.lang.StackOverflowError

workflow.2102.delta.repository

APAR status

• Closed as program error.

Error description

• The bootstrapProcessServerData command provokes a circular loop
  when "service-tracking-enabled" is set to false in the
  100Custom.xml and fails with the following error:
  1/19/21 10:07:11:865 CST] 00000001 Registry     E  CWLLG2035E:
  The registry was not initialized.  Error:
  java.lang.StackOverflowError
                                  java.lang.StackOverflowError
  followed by:
  Caused by: java.lang.NullPointerException
   at
  com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
  rt.isInTransaction(ProgrammaticTransactionSupport.java:1123)
   at
  com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
  rt.execute(ProgrammaticTransactionSupport.java:400)
   at
  com.lombardisoftware.utility.spring.ProgrammaticTransactionSuppo
  rt.execute(ProgrammaticTransactionSupport.java:342)
   at
  com.ibm.bpm.bootstrap.InstallationGuidHelper.loadInstallationGui
  d(InstallationGuidHelper.java:42)
  In the 100Custom.xml, we can see that the following setting:
  <service-tracking-enabledmerge="replace">false
  </service-trackin g-enabled>
  This means means that no tracking data will be emitted by the
  service flows. A change was done in BAW 20.0.0.2 to set
  service-tracking-enabled by default to "false" to always avoid
  the service flow engine to emit tracking data when running on
  Containers because PDW is not supported on BAW on Containers.
  This setting provokes a loop when getting the
  service-tracking-enabled property value when running the
  bootstrapProcessServerData command.
  

Local fix

• n/a
  

Problem summary

• When the service-tracking-enabled property is configured in the
  100Custom.xml file, running the bootstrapProcessServerData
  command fails with a java.lang.StackOverflowError exception.
  

Problem conclusion

• A fix is available or will be available that ensures running the
   bootstrapProcessServerData command doesn't fail when the
  service-tracking-enabled property is configured in the
  100Custom.xml file.
  

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:

Fix information

• Fixed component name

  BUS AUTO WORKFL

• Fixed component ID

  5737H4100

Applicable component levels