-
Bug
-
Resolution: Done
-
Major
-
7.1.0.ER1
-
None
When the HC builds the boot commands for a server on initial boot there is no logging.properties file in the servers data directory. There's an attempt to discover which configuration file would be used. On some OS's the paths may be the same, but the string representation may be different due to different file separators. When attempting to decide which logging configuration file to use the match may fail which will lead to an incorrect configuration file being used on initial boot only.
- clones
-
WFCORE-2964 Building server boot commands in the HC may use the incorrect logging.properties on initial boot
- Resolved
- is incorporated by
-
JBEAP-11466 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta28
- Closed
- relates to
-
JBEAP-10552 CONSOLE handler in Domain "full-ha" profile
- Closed