IBM Support

JR57555: YOU RECEIVE A NULLPOINTEREXCEPTION WHEN VALIDATING YOUR DEPLOYMENT ENVIRONMENT AFTER MANUALLY CHANGING ORACLE DATABASE URLs

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After you manually change the Oracle database URLs for the IBM
    Business Process Manager (BPM) data sources instead of using the
    "BPMConfig -update -dataSource" command and the database name
    (service name or system ID) in the customized URL uses a
    different capitalization than was originally used in the
    configuration properties file, you receive a
    NullPointerException like the following example when running the
    "BPMConfig -validate" command (or when using the Health Center
    in the WebSphere administrative console):
    
    [1/19/17 11:33:57:394 AEDT] 00000001 BPMConfig     E
    com.ibm.bpm.config.BPMConfig main <Null Message>
                                     java.lang.NullPointerException
     at java.util.ArrayList.addAll(ArrayList.java:571)
     at
    com.ibm.bpm.config.capability.ProvisionDe.healthCheck(ProvisionD
    e.java:535)
     at
    com.ibm.bpm.config.BPMConfig.healthCheck(BPMConfig.java:3761)
     at
    com.ibm.bpm.config.BPMConfig$Actions.healthCheck(BPMConfig.java:
    4992)
     at
    com.ibm.bpm.config.cli.ValidateAction.runInner(ValidateAction.ja
    va:178)
     at
    com.ibm.bpm.config.cli.AbstractConfigAction.run(AbstractConfigAc
    tion.java:129)
     at
    com.ibm.bpm.config.cli.ValidateAction.run(ValidateAction.java:37
    )
     at com.ibm.bpm.config.BPMConfig.main(BPMConfig.java:293)
    

Local fix

  • Manually update the Oracle database name in the IBM BPM data
    source URLs to exactly match their capitalization in the
    cell-bpm.xml file.
    

Problem summary

  • The Oracle database name (service name or system ID) is stored
    in two different configuration files. The validation code did a
    case-sensitive comparison of the database names when searching
    for data sources and, therefore, couldn't match database names
    with different capitalization. Not finding a required data
    source caused a NullPointerException.
    

Problem conclusion

  • A fix will be available in IBM BPM V8.5.7 cumulative fix 2017.03
    that updates the validation code to match Oracle database names
    in a case insensitive manner.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR57555

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    857

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-08

  • Closed date

    2017-03-29

  • Last modified date

    2017-03-29

  • 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

    BPM STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R857 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":"857","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
29 March 2017