You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Jochen Kramer <kr...@thales.de> on 2001/08/02 16:57:42 UTC
xml-parser problems?
Hey,
are there any known Problems with the new Xerces 1.4.2,
using log4j1.1.3?
thanks for reply,
jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org
Re: xml-parser problems?
Posted by Jochen Kramer <kr...@thales.de>.
Wow,
many many thanks and a virtual beer for you, timothy.
We could run the program with ulimit -s 2048,
jdk1.3.1 under suse7.2.
ps. never really thought of a log4j problem,
did a really good job so far.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org
RE: xml-parser problems?
Posted by Timothy Mulle' <tm...@iname.com>.
Everyone,
I did find an article in Sun's Bug Database for Java that people where
having seg faults on Linux machines with JDK1.3. While they didn't
specificly say the Xerces.jar was the problem, a couple of people did
mention that it WAS in their classpath and were using it
such as I had.
It turns out there is some kind of stack issue with the JDK and linux
machines..and you can fix it by running "ulimit -s 4096".
When I had this problem with another application that used Xerces..(ANT) it
appears that it may be Xerces causing the problem with memory size when it
parses the XML..
http://java.sun.com/j2se/1.3/install-linux-sdk.html#problems
Anyway, just thought I'd share the info and hope it helps, it took me a long
time for figure this out..
- Tim
-----Original Message-----
From: kramer@pernambuco.thales.de [mailto:kramer@pernambuco.thales.de]On
Behalf Of Jochen Kramer
Sent: Friday, August 03, 2001 5:56 AM
To: LOG4J Users Mailing List
Subject: Re: xml-parser problems?
Hey, thanks for reply.
for testing purposes we use a command line app. Testing our
XMLWriter made it necessary to install a parser supporting the DOM2
API.
We had no trouble logging via log4j before, but it seems to be
the log4j logger line in the XMLWriter code which brings us a strange
segFault.
without the logger statement the test app finish successfully.
we use the domconfigurator to initialize logging.
tecs:
linux kernel 2.4.6
log4j 1.1.3
xerces 1.4.2
>
> Jochen,
>
> Not to my knowledge no. What seems to be a problem?
>
> At 16:57 02.08.2001 +0200, Jochen Kramer wrote:
> >Hey,
> >
> >are there any known Problems with the new Xerces 1.4.2,
> >using log4j1.1.3?
> >
> >thanks for reply,
> >jochen
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: log4j-user-help@jakarta.apache.org
>
> --
> Ceki Gülcü - http://qos.ch
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org
Re: xml-parser problems?
Posted by Jochen Kramer <kr...@thales.de>.
Hey, thanks for reply.
for testing purposes we use a command line app. Testing our
XMLWriter made it necessary to install a parser supporting the DOM2
API.
We had no trouble logging via log4j before, but it seems to be
the log4j logger line in the XMLWriter code which brings us a strange
segFault.
without the logger statement the test app finish successfully.
we use the domconfigurator to initialize logging.
tecs:
linux kernel 2.4.6
log4j 1.1.3
xerces 1.4.2
>
> Jochen,
>
> Not to my knowledge no. What seems to be a problem?
>
> At 16:57 02.08.2001 +0200, Jochen Kramer wrote:
> >Hey,
> >
> >are there any known Problems with the new Xerces 1.4.2,
> >using log4j1.1.3?
> >
> >thanks for reply,
> >jochen
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: log4j-user-help@jakarta.apache.org
>
> --
> Ceki Gülcü - http://qos.ch
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org
Re: xml-parser problems?
Posted by Ceki Gülcü <cg...@qos.ch>.
Jochen,
Not to my knowledge no. What seems to be a problem?
At 16:57 02.08.2001 +0200, Jochen Kramer wrote:
>Hey,
>
>are there any known Problems with the new Xerces 1.4.2,
>using log4j1.1.3?
>
>thanks for reply,
>jochen
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-user-help@jakarta.apache.org
--
Ceki Gülcü - http://qos.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-user-help@jakarta.apache.org