Skip to main content
NetApp Knowledge Base

The OCI services do not deploy correctly after an OS reboot

  1. Last updated
  2. Save as PDF
Views:
218
Visibility:
Public
Votes:
1
Category:
oncommand-insight
Specialty:
oci
Last Updated:

Applies to

  • OnCommand Insight (OCI) 7.3.9
  • Windows Operating System

Issue

  • After an OS reboot the SANSCREEN services are not deployed
  • There is an error in the server.log:

<date> ERROR [ServerService Thread Pool -- 97] ComposeStartUp (ComposeStartUp.java:251) - Failed to run health checks at startup
org.jboss.as.ejb3.component.EJBComponentUnavailableException: WFLYEJB0421: Invocation cannot proceed as component is shutting down
at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:59) ~[wildfly-ejb3-20.0.1.Final.jar!/:20.0.1.Final]

  • The WAR files fail to deploy because of a timeout:

2021-11-08 00:41:48,241 ERROR [DeploymentScanner-threads - 2] management-operation (AbstractOperationContext.java:1525) - WFLYCTL0190: Step handler org.jboss.as.server.deployment.DeploymentHandlerUtil$1@64277150 for operation deploy at address [("deployment" => "upload.war")] failed -- java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.