OMi DPS startup stuck at mercuryAS

  • Document ID:KM03756349
  • Creation Date:29-Oct-2020
  • Modified Date:12-May-2021
    • Micro Focus Products:
      operations bridge manager 10.63

Summary

DPS does not start, stuck at the jboss, after patch installation

Question

DPS mercuryAS (jboss) process doesn’t start

On the nanny_all.log under <OM_HOME>\log\supervisor

Could not connect to remote://127.0.0.1:9999. The connection failed

Answer

A corrupted module.xml file for the application server can’t be parsed by the jboss component, preventing the startup of the service

 

To address the problem

 

Delete the corrupted module.xml file and let the system recreate it during startup

            On the DPS perform the following

 Stop the services

 Navigate to

   <OMI_HOME>/application-server/modules/system/layers/base/com/hp/bsm/platform/main/

 Delete the module.xml file

Start the OMi services (the file will be created by the system)