[ mx4j-Feature Requests-1223039 ] Support for JDK 5.0? (possible memory leak in DOM/XML)

Feature Requests item #1223039, was opened at 2005-06-18 00:00
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450650&aid=1223039&group_id=47745

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Tools: HTTP Adaptor
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Kurt (kleucht)
Assigned to: Nobody/Anonymous (nobody)
Summary: Support for JDK 5.0? (possible memory leak in DOM/XML)

Initial Comment:
This is not technically a Feature Request, nor is it 
technically a Bug, since you build MX4J using JDK 
1.4.2.  

I use MX4J on one of my projects basically only for it's 
HTTP Adaptor.  For reasons that aren't yet crystal clear 
to me, that project recently got upgraded from JDK 1.4.2 
to JDK 5.0.  Rather than have to switch back & forth 
between two separate compiler versions, I got rid of my 
old JAVA compiler and switched over to 5.0 completely.  
Aside from a few extra compiler warnings, everything 
seemed to be working okay after the switch.

But a week after delivering a new version of our product 
to our customer, we got a report of a very easily 
repeatable OutOfMemory error.  To make a long story 
short, it turns out that every time someone 
requests/receives the main HTML page from the MX4J 
HTTP Adaptor service (http://localhost:8080/), the Heap 
Usage of the app goes up and cannot be recovered ... 
not even via forced garbage collections.

As a minimal test, I just ran only the example 
HttpAdaptor code that is part of the MX4J code tree, and 
I was able to get the OutOfMemory failure by refreshing 
that example app about 100 times on my IE browser.  
You should be able to easily repeat this test by 
installing JDK 5.0 and then running your HttpAdaptor 
example.  Then I reinstalled the old JDK 1.4.2 and did 
the same test, but the failure never occurred ... not even 
after over 500 refreshes.  

I'm very far from being an expert in memory profiling and 
memory leak determination.  Some memory profiler 
software that I ran told me that something was holding 
on to references to DOM and/or XML Objects, but I 
couldn't get any more specific data than that from my 
tools.  I get the feeling that the tools were trying to tell 
me that com.sun.org.apache... type Classes were 
holding on to the references, but I'm not an expert in 
these memory profiling tools.  I know just enough to be 
dangerous.  

Have the MX4J developers ever tried MX4J under JDK 
5.0?  Have you seen the DOM/XML memory leak I am 
describing?  Is there something that can be "fixed" in 
the MX4J code to make this problem go away? Is this a 
SUN bug that someone much smarter than me ought to 
report to SUN?

Thanks for your time,
Kurt (from sunny Central Florida)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450650&aid=1223039&group_id=47745


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click