RE: mod_jserv/5172: Out of Memory exception at org.apache.jserv.J ServConnection.processRequest

[Thomas Fleischmann <tf...@decisive.com>]

The following reply was made to PR mod_jserv/5172; it has been noted by GNATS.

From: Thomas Fleischmann <tf...@decisive.com>
To: "'ed@apache.org'" <ed...@apache.org>
Cc: "'apbugs@Apache.Org'" <ap...@Apache.Org>
Subject: RE: mod_jserv/5172: Out of Memory exception at org.apache.jserv.J
	ServConnection.processRequest
Date: Tue, 19 Oct 1999 16:13:40 -0700

 My servlet does not seem to have memory leaks. Under a normal load, the
 servlet is working fine during hours and the JVM process is not growing in
 size.
 It's only when I put to a heavy load on the system that this exception is
 thrown.
 
 If it does not come from Jserv, why the exception is always thrown at 
 org.apache.jserv.JServConnection.processRequest ?
 
 Thanks for advising!
 
 -----Original Message-----
 From: ed@apache.org [mailto:ed@apache.org]
 Sent: Tuesday, October 19, 1999 4:05 PM
 To: ed@apache.org; jserv-bugdb@apache.org; tfleischmann@decisive.com
 Subject: Re: mod_jserv/5172: Out of Memory exception at
 org.apache.jserv.JServConnection.processRequest
 
 
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
 
 
 Synopsis: Out of Memory exception at
 org.apache.jserv.JServConnection.processRequest
 
 State-Changed-From-To: open-closed
 State-Changed-By: ed
 State-Changed-When: Tue Oct 19 16:04:43 PDT 1999
 State-Changed-Why:
 This is not a bug in JServ: it is most likely a bug in your
 servlet.  (Though it's also possible that the JVM leaks,
 I don't think that's the case with Solaris/1.2.)  It's also
 possible that the servlet uses lots of memory, which would
 eventually get freed if you weren't stress testing it.
 
 There are several things which you can do to debug this,
 but the first is to examine the size of the JVM process
 at the time when the exception occurs.
 
 If it's 64MB, then it doesn't matter how much free memory
 you have in the system.  To work around that, you could
 increase the amount of available memory beyond 64MB (up
 to, say, 128 MB).
 
 To see if your servlet is leaking memory, make repeated
 requests and observe the memory footprint.  If you find
 that it rises linearly with the number of requests (until
 it gets an out of memory error) then you know that's the
 problem.
 
 thanks for using JServ --
 
 Ed
 Class-Changed-From-To: sw-bug-mistaken
 Class-Changed-By: ed
 Class-Changed-When: Tue Oct 19 16:04:43 PDT 1999