[ mx4j-Bugs-1309695 ] OutOfMemoryError in Java 1.5 on Refresh

Bugs item #1309695, was opened at 2005-09-30 20:57
Message generated for change (Settings changed) made by simonebordet
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=450647&aid=1309695&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: HTTP Adaptor
Group: Release 3.0.1
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Michael Starkie (mstarkie)
Assigned to: Nobody/Anonymous (nobody)
Summary: OutOfMemoryError in Java 1.5 on Refresh

Initial Comment:
Hi Everyone,
I have encountered a serious problem when using the
MX4J 3.0.1  HttpAdaptor on java 1.5. 

If I refresh a  page enough times the virtual machine
will eventually throw OutOfMemoryError. 

Running the same program on java 1.4 will always
recover it's memory and never through the error. 

I have created a small test program with readme, build
and run scripts which will demonstrate the error if you
have java 1.4 and 1.5 both installed.  I used windows
xp to test. 

You must supply the 3.0.1 mx4j.jar and mx4j-tools.jar
and place them in the classpath to run the test program.

Since all of our production servers use mx4j and we are
in the process of migrating to java 1.5 I'm hoping
there will be a fix soon.


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

Comment By: Michael Starkie (mstarkie)
Date: 2005-10-03 22:09

Message:
Logged In: YES 
user_id=889192

The memory problem seems to go away when including the
Xalan-J 2.7.0 jar files in the regular application classpath
and removing them from the jvm bootclasspath.

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

Comment By: Michael Starkie (mstarkie)
Date: 2005-10-03 21:43

Message:
Logged In: YES 
user_id=889192

The memory leakage goes away under jprofiler when using the
latest Xalan-j 2.7.0 parsers and pre-prepending them to your
application classpath.  I downloaded the binary distribution
from apache at http://xml.apache.org/xalan-j/downloads.html
and included the jars files in the boot classpath for the
jvm as follows:

-Xbootclasspath/p:xml-apis.jar;xercesImpl.jar;serializer.jar;xalan.jar;mx4j.jar

I'm not sure why this didn't happen with java 1.4 but it
fixes it for 1.5.

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

Comment By: Michael Starkie (mstarkie)
Date: 2005-10-03 20:06

Message:
Logged In: YES 
user_id=889192

This may be a memory leak inside the jvm.  I looked at it
briefly using jprofiler and noticed that the classes that
were not being cleaned up appear to be in the xerces parser
which is included with the jdk. 

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

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


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information