+++ This bug was initially created as a clone of Bug #1031129 +++
Description of problem:
When defining servers with directory-grouping="by-type" the wrong directory is used in the ManagedServerBootCmdFactory. This causes the domain/configuration/logging.properties to always be used which is the incorrect configuration to use.
Steps to Reproduce:
1. Edit the hosts.xml and add the directory-grouping="by-type" attribute
2. Start the domain servers
3. Restart the domain servers
domain/logs/server-one/server.log gets overwritten instead of appended
The log file should be appended.
A workaround is to edit the BOOT_LOG handler in the domain/configuration/logging.properties file or add a logging.properties file to the domain/servers/server-one/data directory.
--- Additional comment from James Perkins on 2013-11-15 13:16:10 EST ---
Pull request sent https://github.com/jbossas/jboss-eap/pull/701
--- Additional comment from JBoss JIRA Server on 2013-11-22 17:55:06 EST ---
James Perkins <firstname.lastname@example.org> made a comment on jira WFLY-2514
Pull request merged
--- Additional comment from mark yarborough on 2013-12-16 08:08:33 EST ---
Flushing remnants of obsolete CP0a nomenclature.
--- Additional comment from Carlo de Wolf on 2014-01-08 04:40:40 EST ---
Removing from eap62-cp01-blockers. If this is meant for a CP, please clone the BZ, set the blocks again and reset target release and milestone.
Marking for inclusion in 6.2.1 release notes.
Verified with 6.2.1.CP.CR1-patch.
Set 'Version' field to ensure this ticket appears in documentation effort dashboards.
Hey Carlo. Can I get some more info on what was causing this bug and how it was resolved? Any help is greatly appreciated.
Marking as incomplete release note for 6.2.1.
In the absence of SME input, I have completed this ticket's release notes entry based on the comments in the ticket's history, also the associated pull request.