You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-user@logging.apache.org by Marc Rossi <mr...@gmail.com> on 2006/12/02 06:15:10 UTC

XMLSocketAppender

Hi all.  Trying to get log4cxx to work with chainsaw.  From what I understand
XMLSocketAppender has to be used, not SocketAppender due to binary format
issues.    When using XMLSocketAppender I have connections established & torn
down, but no data gets sent (double checked with Ethereal).

After digging through archive discovered that the 'os->write(..)' call in the
renderEvent method is commented out -- so no messages get sent.  What is the
timeframe to have this piece of code back online?

TIA,
Marc



Re: XMLSocketAppender

Posted by Curt Arnold <ca...@apache.org>.
On Dec 3, 2006, at 4:28 PM, Marc Rossi wrote:

>
> Went ahead and added the following line to the end of the
> XMLSocketAppender::renderEvent() method:
>
>     os1->write(output)
>
> and it is now sending out the xml event info (although it still isn't
> displaying properly in chainsaw).  Not sure why this line wasn't  
> already
> there (almost the same line was commented out in the original source).
>

Logged and resolved as http://issues.apache.org/jira/browse/ 
LOGCXX-164.  Also logged https://issues.apache.org/jira/browse/ 
LOGCXX-165 as the original 0.9.7 and the current implementation could  
result in corrupted XML due to a mismatch of the expected UTF-8  
encoding and the actual encoding, however fixing that would probably  
warrant a complete review of SocketAppender and XMLSocketAppender in  
log4cxx.

The code using the Microsoft Platform SDK macro T2A was removed  
during the migration to supporting both single char and wide char  
logging simultaneously.  It just wasn't restored when things were put  
back together.



Re: XMLSocketAppender

Posted by Marc Rossi <mr...@gmail.com>.
Went ahead and added the following line to the end of the
XMLSocketAppender::renderEvent() method:

    os1->write(output)

and it is now sending out the xml event info (although it still isn't
displaying properly in chainsaw).  Not sure why this line wasn't already
there (almost the same line was commented out in the original source).



Marc Rossi wrote:
> 
> Marc Rossi <mrossi19 <at> gmail.com> writes:
>> Hi all.  Trying to get log4cxx to work with chainsaw.  From what I
>> understand
>> XMLSocketAppender has to be used, not SocketAppender due to binary format
>> issues.    When using XMLSocketAppender I have connections established &
>> torn
>> down, but no data gets sent (double checked with Ethereal).
>> 
>> After digging through archive discovered that the 'os->write(..)' call in
>> the
>> renderEvent method is commented out -- so no messages get sent.  What is
>> the
>> timeframe to have this piece of code back online?
> 
> I checked the JIRA issue page for this project and didn't see anything
> similar
> to what I have described.  
> 
> 
> 
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/XMLSocketAppender-tf2742085.html#a7668080
Sent from the Log4cxx - Users mailing list archive at Nabble.com.


Re: XMLSocketAppender

Posted by Marc Rossi <mr...@gmail.com>.
Marc Rossi <mrossi19 <at> gmail.com> writes:
> Hi all.  Trying to get log4cxx to work with chainsaw.  From what I understand
> XMLSocketAppender has to be used, not SocketAppender due to binary format
> issues.    When using XMLSocketAppender I have connections established & torn
> down, but no data gets sent (double checked with Ethereal).
> 
> After digging through archive discovered that the 'os->write(..)' call in the
> renderEvent method is commented out -- so no messages get sent.  What is the
> timeframe to have this piece of code back online?

I checked the JIRA issue page for this project and didn't see anything similar
to what I have described.