-
Bug
-
Resolution: Unresolved
-
Major
-
None
File standalone-full.xml can be configured via cli but it does not have the desired effect of producing logs;
As specified in the RFE, the server is reloaded after changes;
We verified that with the following:
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
or
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
: no file standalone/log/ejb-access.log is produced;
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
or
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
: no logs in standalone/log/server.log;
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
: no logs in console;
