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.