Anyone run into issues patching from P06 to P08 on version of RSA IGL 7.1.0?
I get this error below. I tried extending it from 15 mins to 30 mins, but still no luck/
I tried extending it from 900 (15min) to 1800 (30
File: /home/oracle/Aveksa_7.1.0_P08/deploy/wildfly-conf/groovy/com/aveksa/wildfly/CustomizeACM.groovy
Original:
def addCmd = "${AVEKSA_HOME}/wildfly/bin/jboss-cli.sh -c --command=/system-property=jboss.as.management.blocking.timeout:add(value=900)"
Changed To:
def addCmd = "${AVEKSA_HOME}/wildfly/bin/jboss-cli.sh -c --command=/system-property=jboss.as.management.blocking.timeout:add(value=1800)"
=================================================================================
Patch Log (Error):
Creating aveksa.ear file for deployment
[zip] Building zip: /tmp/customizeACM/aveksa.war
[zip] Building zip: /tmp/customizeACM/aveksa.ear
[copy] Copying 1 file to /home/oracle/archive
Undeploying current ear...
Undeploy failed: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0216: Management resource '[(\"deployment\" => \"aveksa.ear\")]' not found"}}
Deploying new customized ear... this may take a while...
Exception encountered while deploying Aveksa.ear
WFLYCTL0344: Operation timed out awaiting service container stability
Aveksa.ear deployment failed after 15 minutes, 22.993 seconds
Updating CURRENTLY_DEPLOYED_ARCHIVE to aveksa_7.1.0_143825_P08-2019-Sep-13-10.14.ear
aveksa_7.1.0_143825_P08-2019-Sep-13-10.14.ear archived
An error occured in the customizeACM command : error code 5
Error deploying the ear file
Step failed! See /home/oracle/Aveksa_7.1.0_P08/logs/7.1.0_P08_2019-09-13-1010.log for more information.
There was an issue in early 7.1.0 builds where the WildFly timeout value was set to 300 seconds (5 minutes) which was not long enough for some customer deployments. Although the deployment should finish in a couple of minutes, some systems were taking slightly over 5 minutes. All current builds of the product have the timeout set to 900 seconds (15 minutes) which is much longer than is required for any deployment type.
If the Wildfly deployment does not finish in 15 minutes, then it will not finish in any length of time. Increasing the timeout value longer will not resolve the issue.
There is some incompatibility in the customers EAR file that is preventing successful deployment. You can attempt to troubleshoot the reason but there is no logging for this aspect of the WildFly operation. If you do identify the issue, likely the problem will require you to discard the EAR file as it is likely unrecoverable.
The fastest solution in these situations is just to restore the ear file from a known good version. Customer customization (JDBC drivers and jsp's) will have to be applied again.
There are several techniques to deploy a new EAR. I recommend deploying the 7.1.0 GA EAR file and then patching again.