lack of memory

["Grübel, Nicole" <Ni...@huk-coburg.de>]

I just got told that it seems our system-memory gets overloaded by
Java-Xerces. 
Does anybody have any idea this can occur? Could it be a problem with my
configuration or with our applications that are using it?
We are currently using Java VisualAge 3.5.3 with Log4J 1.1.3

Thanks for any advice!


Nicole

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: lack of memory

[davout <da...@dsl.pipex.com>]

I've stepped across a problem in the past where Xerces it doesn't seem to
release objects associated with DOM trees, i.e. 'Document'.

We had a junit based test harness that was running out of memory. We put a
profiler on the code and found that there were a ton of Doucment instances
hanging unreleased. This is even after all our code explicitly set all
'Document' and 'Node' class data members to 'null'

With Java its hard to tell whether this is a real bug or just the garbage
handler being a bit slow

-----Original Message-----
From: Grübel, Nicole [mailto:Nicole.Gruebel@huk-coburg.de]
Sent: 25 July 2002 09:41
To: Log4J Users List
Subject: lack of memory


I just got told that it seems our system-memory gets overloaded by
Java-Xerces.
Does anybody have any idea this can occur? Could it be a problem with my
configuration or with our applications that are using it?
We are currently using Java VisualAge 3.5.3 with Log4J 1.1.3

Thanks for any advice!


Nicole

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>