A bug fix in the StringBuffer in 1.4.0 (carried into 1.4.1) triggered a memory leak bug. Basically, reusing a StringBuffer kept allocating fresh memory for the new contents, but did not release old memory. Certain Servlet containers, including (but most definately NOT limited to Jetty) relied very heavily on the freshly broken object, as they use StringBuffers to put together the HTML reponses. This has been fixed, but I think only for the 1.4.2 (and maybe the latest 1.4.1). Search the BugParade for closed StringBuffer Memory Leak bugs.
Regards, Steve
Hunter Hillegas wrote:
Yeah... I watched the java process go from 256MB to 512MB to 1.5GB of used memory and then crash...
Reverting back to 1.4.0 saved us...
1.4.2 fixes a couple of bad memory leaks so I'm hoping that will let us move forward again.
From: "Bill Burke" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Thu, 5 Jun 2003 16:54:23 -0400 To: <[EMAIL PROTECTED]> Subject: RE: [JBoss-user] Jetty OutOfMemoryError
Seriously? I've been on 1.4.1_02 for awhile on Linux RH8. Seems ok. Of course, I'm just doing development and testing on it, although I did run ECPerf once.
Bill
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Hunter Hillegas Sent: Thursday, June 05, 2003 2:04 PM To: JBoss User Subject: Re: [JBoss-user] Jetty OutOfMemoryError
Running on Linux?
Try 1.4.0_x
We had problems with 1.4.1.
From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Date: Thu, 5 Jun 2003 19:22:23 +0200 (CEST) To: [EMAIL PROTECTED] Subject: [JBoss-user] Jetty OutOfMemoryError
Hi,
I am taking some pressure on a web app which is running under JBoss3.2.0/Jetty???.
I can reproduce the following error:
java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start(Native Method) at org.mortbay.util.ThreadPool$PoolThread.enterPool(ThreadPool.java:385) at org.mortbay.util.Pool.newPondLife(Pool.java:339) at org.mortbay.util.Pool.get(Pool.java:276) at org.mortbay.util.ThreadPool.run(ThreadPool.java:319) at org.mortbay.util.ThreadedServer$Acceptor.run(ThreadedServer.java:515)
19:17:58,900 WARN [jbossweb] WARNING: Stopping Acceptor ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=8080]
This happens at once if the pressure test is started. The JVM memory should be ok since Xmx and Xms params are initialized with 512MB and 1024MB. I checked JDK1.4.1_01 and JDK1.4.1_03. I also checked the Jetty version shipped with 3.2.1. Same errors.
Does Jetty have a memory leak here?
Thanks,
-marek
-- Java/J2EE Developer/Integrator 214-724-7741
------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
