----------------------------------------------------------------
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 tried 2 JRE :
- SUN 1.1.8
- SUN 1.2.2 (final)
I tried :
wrapper.bin.parameters=-Xms64m -Xmx64m
/*******************************************************************************/
important note : the startup is always ok :
---------> [25/02/2000 16:02:00:021 CET] <servletLog> hello/IsItWorking:
started
/*******************************************************************************/
but always the same problem when invoking anything like :
- http://hostname/servlets/IsItWorking
- http://hostname/servlets/
- http://hostname/servlet/
even with
- http://hostname/servlets/xxxxxx
where xxxxxx is anything !!!!
---------> [25/02/2000 16:02:31:323 CET] <jservException> AJP Protocol
Error: java.io.IOException: Stream closed prematurely
Please, help me !
"Riley, Cameron" a écrit :
>
> ----------------------------------------------------------------
> 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!!!
> ----------------------------------------------------------------
>
> >"AJP Protocol Error: java.io.IOException: Stream closed prematurely"
>
> I think you will find this is because the Browser timed out on the
> PrintWriters output Stream before the stream had been closed. The JVM most
> likely had taken too long to load and execute the Servlet you are hitting.
> The most obvious solution is get more RAM. You can also try allocating the
> JVM more memory from the jserv.conf file;
>
> wrapper.bin.parameters=-Xms64m -Xmx64m
>
> where 64 is the amount of RAM available to the JVM, up it as far as you can.
> Alternatively try preloading the Servlets you are going to hit at your zones
> initialization. In your_zone.properties edit the startup directive;
>
> servlets.startup=name_of_servlet
>
> When you hit the Servlet, it should have been loaded into the JVM's memory
> already. The other alternative is try different JVM's. We have found that
> different JVM's give differing performance in different situations. It may
> be the JVM is causing your system to bog down.
>
> Cameron Riley
>
> --
> --------------------------------------------------------------
> 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]
