DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40161>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40161

           Summary: SysLogAppender is not logging header of the layout
           Product: Log4j
           Version: 1.2
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: major
          Priority: P2
         Component: Appender
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


Hi Log4j-Dev,

Bug Description:
I am using SyslogAppender to redirect the application specific logs to Unix
Syslog but I am unable to find the Header of the Custom layout in 
Syslogs.Currently I am using log4j 1.2.8

Observation:
When I observe other appenders they are extending WriteAppender class which 
has writeHeader() funtion to log the Header.But I found that this functionality
is missing in SyslogAppender.

So when I simply use the SyslogAppender with the extra function WriteHeader()
and just append to the writerlayout.getHeader().I am able to log the header

I have seen that this funtionality is even missing in log4j 1.2.13.


If I am not wrong Can you please let me know whether there is any possibility 
of logging the header information with the existing verison(Currently I am 
using log4j 1.2.8.) or When can I get the required funtionality in log4j 
builds because my application is unabling the cilents to configure the logs

Waiting to find the fix in log4j builds soon


Thanks and Regards,
Aparna

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to