----------------------------------------------------------------
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!!!
----------------------------------------------------------------
Ben,
Can you also include the script you are using for the stress testing ?
I can try and run it on my machine and see what turns up.
best regards
Raghu
From:"B. Flaumenhaft" <[EMAIL PROTECTED]> on 01/18/2000 07:37 PM GMT
Sent by: "B. Flaumenhaft" <[EMAIL PROTECTED]>
Please respond to "Java Apache Users"
<[EMAIL PROTECTED]>
To: "Java Apache Users" <[EMAIL PROTECTED]>
cc: (bcc: Raghu V Singh/rsingh1/LSU)
Subject: Re: Apache/JServ under high-volume requests?
----------------------------------------------------------------
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!!!
----------------------------------------------------------------
Thanks for all the suggestions, but I'm afraid I've managed to duplicate
the problem with an extremely basic servlet (no database access or
potential resource issues).
I took the SimpleServlet program, included as an example in the JSDK. This
servlet simply opens an output stream and prints a "hello world"; I added a
small delay to it (Thread.sleep() for ten seconds). Several hundred
connections kills Apache/JServ quite effectively.
I've attached this servlet code to the end of this message, in case anyone
would like to try it for themselves.
It certainly occurred to me that there might be bugs in my code (or in my
VM). Still, to reiterate what noone has responded to: *** I'm not seeing
deadlock, and I'm not seeing exceptions. I'm seeing JServ restart itself
and Apache return internal server errors while this is happening. ***
Under what conditions should JServ die and restart? I was under the
impression that it shouldn't be possible for my code to kill the VM.
I have a number of ideas as to what's happening here (most of them
involving APJserv issues), but they're pure speculation, and I don't know
the JServ internals very well. That's why I'm posting this here.
To reiterate: a very vanilla servlet is killing Apache/JServ under
high-load conditions, and this is perfectly duplicable under Linux and
Solaris (using several VMs, including the JavaSoft VM).
Thoughts?
Thanks,
Ben Flaumenhaft
here's the code that's causing problems when requested by one or two
hundred concurrent threads:
import java.io.*;
import javax.servlet.*;
import javax.servlet.http.*;
public class SimpleServlet extends HttpServlet
{
public void doGet ( HttpServletRequest request,
HttpServletResponse response )
throws ServletException, IOException
{
PrintWriter out;
String title = "Simple Servlet Output";
// set content type and other response header fields first
response.setContentType("text/html");
// then write the data of the response
out = response.getWriter();
out.println("<HTML><HEAD><TITLE>");
out.println(title);
out.println("</TITLE></HEAD><BODY>");
out.println("<H1>" + title + "</H1>");
out.println( "<p> Delaying 10 seconds ..." );
out.flush();
try
{
Thread.sleep( 10 * 1000 );
out.println( "done" );
}
catch( InterruptedException e )
{
out.println( "interrupted" );
}
out.println("<P>This is output from SimpleServlet.");
out.println("</BODY></HTML>");
out.close();
}
}
--
--------------------------------------------------------------
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]
--
--------------------------------------------------------------
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]
