IBM Support

JR54749: DEPLOYMENT MANAGER FAILED TO START AFTER UPGRADE TO BPM V8.5.6.0 CF01 DUE TO BPMUPDATESYSTEMAPP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • The deployment manager fails to start after upgrading to 8.5.6
    CF1. It fails during the bootstrap command.
    
    While reviewing the BPMUpdateSystemApp log files you see it
    fails with this message.
    WASX7093I: Issuing message: "WASX7015E: Exception running
    command: "AdminTask.BPMUpdateSystemApp('[-twxFile]')"; exception
     information:
    
    When looking into the root issue it shows this
    nullpointerexception
    
    java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:60)
     at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:37)
     at java.lang.reflect.Method.invoke(Method.java:611)
     at com.ibm.bpm.pal.commands.impl.internal.BPMUpdateSystemApp.
      fixExistingBPDInstances(BPMUpdateSystemApp.java:544)
     at com.ibm.bpm.pal.commands.impl.internal.BPMUpdateSystemApp.
      doBPMSystemAppUpdate(BPMUpdateSystemApp.java:395)
     at com.ibm.bpm.pal.commands.impl.internal.BPMUpdateSystemApp.
      execute(BPMUpdateSystemApp.java:473)
    ...
    Caused by: java.lang.NullPointerException
     at com.lombardisoftware.server.ejb.persistence.PersistenceServi
       cesCore.findByPrimaryKey(PersistenceServicesCore.java:193)
     ...
    at com.lombardisoftware.client.persistence.common.
      AbstractVersionedPOFactory.findByPrimaryKey
      (AbstractVersionedPOFactory.java:152)
     at com.lombardisoftware.server.ejb.repositoryservices.
      SystemAppUpdateSupport.fixExistingBPDInstances
      (SystemAppUpdateSupport.java:228)
     at com.lombardisoftware.server.ejb.repositoryservices.
      RepositoryServicesCore.fixExistingBPDInstances
      (RepositoryServicesCore.java:556)
    

Local fix

Problem summary

  • Deployment manager fails to start after upgrade to 8560 cf1,
    because BPMUpgradeSystemApp command fails to update governance
    toolkit, as there is no change with with governance toolkit, so
    it will be excluded during upgrade in 8560 CF2
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    JR54749

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    856

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-11-17

  • Closed date

    2015-12-15

  • Last modified date

    2015-12-15

  • 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":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"856","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 December 2015