----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
I had the same problem recently. It was during a demo, when the hard
disk started thrashing about, even though I wasn't doing anything at all
(i.e. not launching any programs, not clicking any buttons, etc.). When
I tried to pull information out of the database, it took a ridiculously
long time, and I lost some credibility there, because in all my previous
tests, JServ performed very snappily.
I have since isolated it down to garbage collection which the IBM JDK
seems to fire at the most inappropriate times <cheesy grin>. If you
write a servlet that is a "straight" connection to the database (first
JDBC example in Jason Hunter's book) you'll see this problem --
eventually. You need to use the second example (the one with database
connection pooling). That'd do the trick.
Regards,
pascal chong
"B. Flaumenhaft" wrote:
> Hello:
>
> After seeing no problems with Apache/JServ on a number of platforms for
> quite a while, I've run into some pretty serious difficulties under
> high-volume situations (load testing, mostly). I'm having trouble figuring
> out where the problem is, though.
>
> Here's the situation (versions and platform specs below):
>
> When I send *lots* of requests to JServ (several hundred concurrent
> requests), I periodically get...
>
> [Tue Jan 11 17:22:12 2000] [error] [client 207.33.124.11] Premature end
> of script headers: /zone/main
>
> ...in the Apache error log. Several hundred requests fly by, each
> receiving the "premature end of script headers error", at which point JServ
> appears to restart (servlet init() methods are called). While the server is
> logging "premature end of script headers", the client gets an Apache
> "Internal server error" response. No further information is given.
>
> I suspect this isn't a problem with the Java code; if it were, I'd be
> seeing a hanging server (if I had thread deadlock or some such), or
> exceptions, or some such. As it is, it seems like the server just chokes
> and restarts when traffic reaches a certain level. (What that level is has
> been very unpredictable.)
>
> Has anyone seen anything like this? I'm at my wit's end, and I'm really not
> eager to go to another web server this close to installation time.
>
> This problem has occurred on several platforms ...
>
> - SunOS 5.7, Apache 1.3.9, ApacheJServ-1.1b3 (Sun Solaris VM
> Solaris_JDK_1.2.1_04)
>
> - Linux (RedHat 6.0), Apache 1.3.9, ApacheJServ-1.1b2 (Blackdown VM
> Linux_JDK_1.2_pre-release-v2)
>
> - Linux (RedHat 5.2), Apache 1.3.3, ApacheJServ-1.0b1 (Blackdown VM
> Linux_JDK_1.2_pre-release-v1)
>
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
