-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
Once a candidate server has been prepared, the users have to restart the server with --perform-installation argument.
This special shutdown will instruct the underlying launch script to execute the apply server candidate phase. In this phase, there are some validation checks executed by the launch script and if those checks and processing are correct, then the launch script will invoke the JBoss EAP installation manager to apply the server candidate.
The script validation is executed without any logging framework, so any information or error will be sent to the standard output or error of the launch script. If the server is running as a service, this will be the log file configured when the server was installed as a service. We should send any console trace to the expected log file instead.
The execution of the JBoss EAP installation manager after the script validation is executed under a logging framework, however, the logger configuration is not correct, so log traces are not sent to the expected files.
- is cloned by
-
WFCORE-6874 Apply server candidate phase logs are not saved in log files when using Management CLI
-
- Resolved
-
- is incorporated by
-
JBEAP-27543 (8.0.z) Upgrade WildFly Core from 21.0.10.Final-redhat-00001 to 21.0.11.Final-redhat-00001 in EAP 8.0 Update 4
-
- Resolved
-