Patching RSA Governance & Lifecycle fails with error Unable to connect to controller.
2 years ago
Article Number
000067946
Applies To
RSA Product Set:  RSA Identity Governance & Lifecycle
RSA Version/Condition: 7.x
Issue
Installing a patch for RSA Identity Governance & Lifecycle in WildFly setup fails with the following error shown in Patch.log
Caught: java.lang.IllegalStateException: Unable to connect to controller.
java.lang.IllegalStateException: Unable to connect to controller.
at org.jboss.as.cli.scriptsupport.CLI.doConnect(CLI.java:306)
at org.jboss.as.cli.scriptsupport.CLI.connect(CLI.java:82)
at org.jboss.as.cli.scriptsupport.CLI$connect$0.call(Unknown Source)
at com.aveksa.wildfly.Util.connect(Util.groovy:157)
at com.aveksa.wildfly.Util$connect.call(Unknown Source)
at com.aveksa.wildfly.CustomizeACM.addLoggingFilters(CustomizeACM.groovy:573)
at com.aveksa.wildfly.CustomizeACM.run(CustomizeACM.groovy:55)
Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:1520)
at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:1296)

... 22 more
An error occured in the customizeACM command : error code 1

 
Resolution
RESOLUTION STEPS:
  • Connect to the server SSH session.
  • ACM stop.
  • Run the command ifconfig to get the server IP address.
  • Go to the path /home/oracle/wildfly/bin/
  • Take a backup of the file jboss-cli.xml by running the command 
cp jboss-cli.xml jboss-cli.xml.bkp
  • Edit the jboss-cli.xml file and replace Localhost with the server IP address.
<default-controller>
<protocol>remote+http</protocol>
<host>localhost</host>
<port>9990</port>
</default-controller>
  • ACM start
  • Install the Patch