-
1. Re: JBoss 7.1.1 does not create server.log.
nazia24 Sep 27, 2013 1:07 AM (in response to kingakoopa)Hi,
path : The actual filesystem path. Treated as an absolute path, unless the relative-to attribute is specified, in which
case the value is treated as relative to that path.
relative-to : An optional attribute indicating the name of another previously named path, or of one of the standard paths
provided by the system.
So, when you give relative-to as "jboss.server.log.dir" and path as "/apps/logs/AppLogix.Cluster/server.log"
<file relative-to="jboss.server.log.dir" path="/apps/logs/AppLogix.Cluster/server.log"/>
then server.log will be created in log folder as : domain/servers/server-name/log/apps/logs/AppLogix.Cluster
---------------------------------
And if you want some other path then you can give direct path as for ex: "/home/Desktop/test"
<file path="/home/Desktop/test/server.log"/>
then log will be created at that specified location.
Hope this helps.......
-
2. Re: JBoss 7.1.1 does not create server.log.
kingakoopa Sep 27, 2013 11:59 AM (in response to nazia24)Nazia , I I thank you sincerely for helping me out on this issue..............
I just tried that and unfortunately it didnt create the logs in the location.
Its still creating the logs under
/apps/jboss/jboss-as-7.1.1.Final/domain/servers/AppLogix.Member1/log
Here is my current confirguration in domain.xml
<profile name="AppLogix-full-ha">
<subsystem xmlns="urn:jboss:domain:logging:1.1">
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
</console-handler>
<periodic-rotating-file-handler name="FILE">
<level name="INFO"/>
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file path="/apps/logs/AppLogix.Cluster/server.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="true"/>
</periodic-rotating-file-handler>
Any other ideas?
-
3. Re: JBoss 7.1.1 does not create server.log.
kingakoopa Sep 27, 2013 12:34 PM (in response to kingakoopa)OK I figured it out
at the bottom of the domain.xml
I had this
<server-groups>
<server-group name="AppLogix.Cluster" profile="full-ha">
<socket-binding-group ref="full-ha-sockets"/>
</server-group>
<server-group name="Skunk.Cluster" profile="full-ha">
<socket-binding-group ref="full-ha-sockets"/>
</server-group>
<server-group name="Garbage.Cluster" profile="full-ha">
<socket-binding-group ref="full-ha-sockets"/>
</server-group>
</server-groups>
All the profiles had the correct locations for the server.log file but there was another profile called full-ha( an un-used useless profile) that will still pointing to the default location. I forgot to change it from full-ha to AppLogix-full-ha & Skunk-full-ha & Garbage-full-ha.
Once I changed it , it all worked fine !!!
<server-groups>
<server-group name="AppLogix.Cluster" profile="AppLogix-full-ha">
<socket-binding-group ref="full-ha-sockets"/>
</server-group>
<server-group name="Skunk.Cluster" profile="Skunk-full-ha">
<socket-binding-group ref="full-ha-sockets"/>
</server-group>
<server-group name="Garbage.Cluster" profile="Garbage-full-ha">
<socket-binding-group ref="full-ha-sockets"/>
</server-group>
</server-groups>
Thanks you so very much Naziya , appreciate your help !!!!