[jboss-jira] [JBoss JIRA] (WFWIP-181) Access logging for EJBs: no logs produced

[Tommasso Borgato (Jira)]

     [ https://issues.jboss.org/browse/WFWIP-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tommasso Borgato updated WFWIP-181:
-----------------------------------
    Description: 
File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;

We verified that with the following:

{noformat}
<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>
{noformat}

: no file {{standalone/log/ejb-access.log}} is produced;

{noformat}
<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>
{noformat}

or

{noformat}
<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>            
{noformat}

: no logs in {{standalone/log/server.log}};

{noformat}
<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>
{noformat}

: no logs in console;  

  was:
File {{standalone-full.xml}} can be configured via cli but it does not produce any log;

We verified that with the following:

{noformat}
<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>
{noformat}

: no file {{standalone/log/ejb-access.log}} is produced;

{noformat}
<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>
{noformat}

or

{noformat}
<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>            
{noformat}

: no logs in {{standalone/log/server.log}};

{noformat}
<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>
{noformat}

: no logs in console;  



> Access logging for EJBs: no logs produced
> -----------------------------------------
>
>                 Key: WFWIP-181
>                 URL: https://issues.jboss.org/browse/WFWIP-181
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: Logging
>            Reporter: Tommasso Borgato
>            Assignee: James Perkins
>            Priority: Blocker
>
> File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
> We verified that with the following:
> {noformat}
> <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>
> {noformat}
> : no file {{standalone/log/ejb-access.log}} is produced;
> {noformat}
> <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>
> {noformat}
> or
> {noformat}
> <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>            
> {noformat}
> : no logs in {{standalone/log/server.log}};
> {noformat}
> <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>
> {noformat}
> : no logs in console;  



--
This message was sent by Atlassian Jira
(v7.12.1#712002)