If a servlet encounters an error during execution JServ starts consuming
huge amounts of cpu cycles and memory.  For instance there was a coding
error with a mistype column name used in a SQL update statement, instead
of going to the Exception handler, the servlet hangs and starts
consuming resources.

This occurs whether the code is within a try - catch block or not.

We moved the code over to a NT configuration and we don't see the same
problem which leads me to believe that it may have something to do with
the JDK?

Configuration:
   OS: Solaris 2.7
   Webserver: Apache 1.3.6
   JServ: Apache JServ 1.0 (final)
   Java 1.2.1 build Solaris_JDK_1.2.1_03, native threads, sunwjit

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to