HTTP 500 error / "java.lang.NullPointerException" in TrueSight Orchestration Operator Control Panel

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    TrueSight Orchestration Platform


    COMPONENT:

    TrueSight Orchestration Platform


    APPLIES TO:

    BMC Atrium Orchestrator Platform, all versions TrueSight Orchestration Platform, all versions



    PROBLEM:

     

    Users cannot view a specific workflow in the BMC Atrium Orchestrator /TrueSight Orchestration (TSO) Operator Control Panel (OCP). Other workflows do load and can run to completion. When the workflow fails to load, the log file aoocp.log records this error:

      

    01 Jan 2018 01:01:01,001 [Thread=http-nio-28080-exec-3] ERROR SoapHandler     : Exception occurred while getting the SOAP response
    java.io.IOException: Server returned HTTP response code: 500 for URL: https://myserver.bmc.com:38080/baocdp/ws/console

      

    In some cases, the OCP also displays a "java.lang.NullPointerException" error after a user logs in.

     


    CAUSE:

    The OCP could not load the workflow, usually because the workflow is in an invalid format or contains another critical error that means the peer and the OCP could not process it.


    SOLUTION:

     

    Open the file [TSO_HOME]/tomcat/logs/grid.log on the peer to which the OCP is pointing (usually your primary Configuration Distribution Peer). This file should have an error like the following with:

      
       
    1. a detailed error,
    2.  
    3. the name of the invalid workflow,
    4.  
    5. the portion of the workflow that is invalid, and
    6.  
    7. the location of that invalid activity within the workflow:
      

    01 Jan 2018 01:01:01,001 [Thread=http-nio-28080-exec-4] WARN  ActivityConfigurable     Ignoring error loading process [ProcessID stringRepresentation=(2) :MyModule:Make Connection]: com.realops.foundation.configuration.ConfigurationException: Message[summary=An archive configuration error occurred., detail=Encountered bad XML format while loading configuration information.]
    com.realops.foundation.configuration.ConfigurationException: Message[summary=An archive configuration error occurred., detail=(1) Encountered bad XML format while loading configuration information.]
    ...Caused by: com.realops.foundation.activityprocessor.activity.InvalidActivityConfigurationException: Message[summary=Unable to manufacture Activity., detail=Unable to manufacture Activity.]
    ...Caused by: java.lang.reflect.InvocationTargetException
    ...Caused by: com.realops.common.xml.InvalidXMLFormatException: Message[summary=XML being processed is invalid., detail=(1) The XML is considered to be in an invalid format, and processing cannot proceed. The XML being processed was: (3) <case><condition /><sequence><assign><meta><documentation /><checkpoint>false</checkpoint></meta><location> (4) :switch[1]:sequence[2]:assign[1]</location></assign></sequence></case>]

      


    In this example, the workflow contains a Switch statement in which one case has no condition. Without a condition, a Switch statement cannot use that case, so the case is incomplete and the workflow is not valid.

    To resolve the error, deactivate the module with the invalid workflow. To prevent the error from occurring again, correct the invalid portion of the workflow.

     


    Article Number:

    000098704


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles