-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
None
-
False
-
-
-
-
-
-
Before CP 5, the EAP server is able to start by using a configuration file that is a soft link to a configuration file that is located outside of the server configuration directory.
This issue is caused by JBEAP-22907 where additional restrictions were added to control where this file can be located.
The issue is JBEAP-22907 is now following the soft links and breaks server configuration environments that were working in CPs < 5
- is caused by
-
JBEAP-22907 (7.4.z) WFCORE-5792 Configuration changes made to embedded server are not stored in expected location
- Closed
- is cloned by
-
WFCORE-5970 Server does not start when configuration file is a soft link to a file outside of the server configuration directory
- Closed
- is incorporated by
-
JBEAP-23802 (7.4.z) Upgrade WildFly Core from 15.0.15.Final-redhat-00001 to 15.0.17.Final-redhat-00001
- Closed