The following comment has been added to this issue:
Author: gian maria romanato
Created: Fri, 15 Oct 2004 2:05 AM
Body:
Hi all, and thanks for your excellent products.
This bug represented a real headache for my company.
We have a number of installation (J2EE applications) that suffered from OutOfMemory
exceptions after a few-days-execution, or during a stress-test session.
We have been looking for a problem in our code for weeks (the application implements
some caching), and only recently we came up with a nice utility called HeapRoots
(http://www.alphaworks.ibm.com/tech/heaproots), which allowed us to examine one of the
memory dumps generated by Websphere Application Server 5.1 after an OutOfMemory.
Well, our application uses a lot of XSLs and XML transformations and after a 24h
stress test, the heap dump contained an instance of XMLReaderManager whose size was
bigger then 500 Mega Bytes.
We finally found this bug report, we applied the patch provided in the attachment to
Xalan-J 2.6.0 codebase, and we stress-tested again the Application. After more then 24
h of stress testing, the allocated memory for the whole server was less then half of
the available ram, whith the garbage collector being invoked every 6-10 seconds
compared to the 2 seconds invocation that occurred with the official 2.6 release of
Xalan.
Now we have this home-built version of Xalan that we can of course deliver to our
clients, but we would rather prefer an official release from Apache Foundation,
containing the mentioned patch.
This bug report states that the bug, although fixed, is not yet present in any
official release.
Is there any scheduled release to be delivered in few days ? If not, is there a chance
that you release a 2.6.1 maintanance version containing this bugfix ?
Thank you very much for your great work.
Gian Maria Romanato.
www.finantix.com
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/XALANJ-1844?page=comments#action_54145
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XALANJ-1844
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XALANJ-1844
Summary: XMLReaderManager provides neither no way to clear its cache nor it clears
its cache by itself
Type: Bug
Status: Resolved
Resolution: FIXED
Project: XalanJ2
Components:
Other
Versions:
CurrentCVS
Assignee: Henry Zongaro
Reporter: Andre Doherty
Created: Wed, 31 Mar 2004 9:59 AM
Updated: Fri, 15 Oct 2004 2:05 AM
Environment: Operating System: All
Platform: All
Description:
Considering a hightly multithreaded system, where threads have a short living
time, and some of the threads perform XSLT transformation, but only once, the
JVM soons reaches memory saturation, since XMLReaders are never re-used.
I would suggest maybe to keep the ThreadLocal mecanism instead of the map +
ThreadLocal duet which appears redondant to me, but maybe i am missing some point ?
André
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
