Skip to main content
NetApp Stage KB

WFA deployment files fail to deploy after reboot, because of VM performance issues

  1. Last updated
  2. Save as PDF

Views:
Visibility:
Public
Votes:
0
Category:
oncommand-workflow-automation-wfa
Specialty:
om
Last Updated:

Applies to

OnCommand Workflow Automation 5.1.1 installed on Windows (WFA)

Issue

  • The deployment files on \<instalation_path>\NetApp\WFA\jboss\standalone\deployments\ are staying in .isdeploying state for long time and then they switch to .failed state.
  • The Web UI is not reachable.
  • In \<instalation_path>\NetApp\WFA\jboss\standalone\log\server.log, after 5 minutes we see the following error:

2021-03-23 11:43:19,845 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[
    ("core-service" => "management"),
    ("management-interface" => "http-interface")

 

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.