IAM went down and stopped all the services - Server shutdown has been requested via an OS signals
search cancel

IAM went down and stopped all the services - Server shutdown has been requested via an OS signals

book

Article ID: 267432

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

Error:

2023-06-02 20:36:30,422 INFO  [org.jboss.as.server] (Thread-2) WFLYSRV0272: Suspending server
2023-06-02 20:36:30,424 INFO  [org.jboss.as.ejb3] (Thread-2) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
2023-06-02 20:36:30,428 INFO  [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested via an OS signals

Environment

All supported DevTest releases and platforms.

Cause

Server machine IAM was running on went down.

Resolution

The server had gone down hence all the services went down as well.

Started up services with no issues.  

Create a script that starts all components automatically on a reboot or a server shutdown.

Here is the order to start the components:

Start Order Sequence

Start the DevTest Server processes (or services) in the following sequence:

  1. Start Identity and Access Manager.
  2. Start the Enterprise Dashboard Server.
  3. Start each Registry.
  4. Start DevTest Portal.
  5. Start the following components in any order:
    • Broker
    • Coordinator server
    • Simulator server that is associated with each coordinator
    • Virtual Service Environment
  6. If used on the DevTest Server, start DevTest Workstation

To shut down the server components, use the reverse order.