I am finding the same trouble than Mike(0xF/EOB-0x17)I would be very
grateful if somebody could suggest some workaround. 


--- Curt Arnold <[EMAIL PROTECTED]> wrote:
> Per the XML 1.0 recommendation, http://www.w3.org/TR/REC-xml/ 
> #charsets,  #x1E is not a valid character and should not occur in an 
> 
> XML document even if escaped as a character entity.  Any XML parser  
> may (might be should or must, but I'd need to check) reject such a  
> document as not being valid XML.  This particular problem is then a  
> bug in log4net, though I suspect that there are similar problems with
>  
> log4j and log4cxx generation of XML logs.
> 
> 
> 
> On Mar 18, 2005, at 7:54 AM, Mike Blake-Knox wrote:
> 
> > I'm using log4net to generate log files that I'm reading with
> > chainsaw. Some of the "text" of a log message may contain control
> > characters (e.g., with a value of 0x1e"). Log4net escapes them as
> XML
> > entinties (e.g., ).
> >
> > When chainsaw using the UdpReceiver tries to parse the log, it
> fails.
> >
> > Here's an example of a complete failing log:
> >
> > <log4j:event  
> >
>
logger="TSYS.BPM.CTI.Server.LoggingServices.Appenders.log4netAppender"
> > timestamp="1111077123337" level="DEBUG"thread="2424">
> >     <log4j:message>[11:22:18]: Sending [AGTLogon C403611980 1 1
> > 2xxxxyyyy].</log4j:message>
> >     <log4j:properties>
> >         <log4j:data
> >
>
name="MessageID"value="TSYS.BPM.CTI.Switch.Mosaix.MosaixIS.Messages.Me
> 
> > ssageSent"
> > />
> >         <log4j:data name="LevelDetail" value="Medium" />
> >         <log4j:dataname="log4japp" value="zzzCTIServer.exe" />
> >         <log4j:data name="log4net:UserName" value="PCS\mblakeknox"
> />
> >         <log4j:dataname="log4jmachinename" value="bpmncprdev4" />
> >         <log4j:data name="log4net:HostName" value="bpmncprdev4"/>
> >     </log4j:properties>
> > </log4j:event>
> >
> > -- 
> > Mike Blake-Knox
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

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

Reply via email to