[
https://issues.jboss.org/browse/AS7-5678?page=com.atlassian.jira.plugin.s...
]
James Perkins updated AS7-5678:
-------------------------------
Description:
Currently if one of the directories (jboss.server.log.dir, jboss.server.tmp.dir or
jboss.server.data.dir) are overridden the directory grouping is ignored. It would be nicer
if the directory grouping was set to {{by-type}} the base directory would be used, but the
{{by-type}} configuration would be honored.
{code}
${JBOSS_HOME}/bin/domain.sh -Djboss.server.log.dir=/var/log/
{code}
host.xml
{code}
<host name="master" xmlns="urn:jboss:domain:1.3">
...
<servers directory-grouping="by-type">
<server name="server-one" group="main-server-group">
</server>
<server name="server-two" group="main-server-group"
auto-start="true">
<!-- server-two avoids port conflicts by incrementing the ports in
the default socket-group declared in the server-group -->
<socket-bindings port-offset="150"/>
</server>
<server name="server-three" group="other-server-group"
auto-start="false">
<!-- server-three avoids port conflicts by incrementing the ports in
the default socket-group declared in the server-group -->
<socket-bindings port-offset="250"/>
</server>
</servers>
</host>
{code}
Should result in a log directory for {{server-one}} of {{/var/log/servers/server-one/}}.
was:
Currently if one of the directories (jboss.server.log.dir, jboss.server.tmp.dir or
jboss.server.data.dir) are overridden the directory grouping is ignored. It would be nicer
if the directory grouping was set to {{by-type}} the base directory would be used, but the
{{by-type}} configuration would be honored.
{code}
${JBOSS_HOME}/bin/domain.sh -Djboss.server.log.dir=/var/log/
{code}
host.xml
{code}
<host name="master" xmlns="urn:jboss:domain:1.3">
...
<servers directory-grouping="by-type">
<server name="server-one" group="main-server-group">
</server>
<server name="server-two" group="main-server-group"
auto-start="true">
<!-- server-two avoids port conflicts by incrementing the ports in
the default socket-group declared in the server-group -->
<socket-bindings port-offset="150"/>
</server>
<server name="server-three" group="other-server-group"
auto-start="false">
<!-- server-three avoids port conflicts by incrementing the ports in
the default socket-group declared in the server-group -->
<socket-bindings port-offset="250"/>
</server>
</servers>
</host>
{code}
Should result in a log directory for {{server-one}} of {{/var/log/server-one/logs/}}.
Honor the directory grouping by-type for domain server directories
------------------------------------------------------------------
Key: AS7-5678
URL:
https://issues.jboss.org/browse/AS7-5678
Project: Application Server 7
Issue Type: Enhancement
Components: Domain Management
Reporter: James Perkins
Assignee: James Perkins
Fix For: 7.2.0.CR1
Currently if one of the directories (jboss.server.log.dir, jboss.server.tmp.dir or
jboss.server.data.dir) are overridden the directory grouping is ignored. It would be nicer
if the directory grouping was set to {{by-type}} the base directory would be used, but the
{{by-type}} configuration would be honored.
{code}
${JBOSS_HOME}/bin/domain.sh -Djboss.server.log.dir=/var/log/
{code}
host.xml
{code}
<host name="master" xmlns="urn:jboss:domain:1.3">
...
<servers directory-grouping="by-type">
<server name="server-one" group="main-server-group">
</server>
<server name="server-two" group="main-server-group"
auto-start="true">
<!-- server-two avoids port conflicts by incrementing the ports in
the default socket-group declared in the server-group -->
<socket-bindings port-offset="150"/>
</server>
<server name="server-three" group="other-server-group"
auto-start="false">
<!-- server-three avoids port conflicts by incrementing the ports in
the default socket-group declared in the server-group -->
<socket-bindings port-offset="250"/>
</server>
</servers>
</host>
{code}
Should result in a log directory for {{server-one}} of {{/var/log/servers/server-one/}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira