----------------------------------------------------------------
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!!!
----------------------------------------------------------------
Michel,
We had something similar happen at webhelp when we
were running out of file descriptors on Linux for our
350,000+ user site. Solution involved a recompile of
the kernel and Apache. I posted this earlier last
month. Basically, we saw that Apache stays up but
JServ goes away with nothing in the logs when we were
peaking.
Also, if you are using native threads make sure you
have JIT turned off: often JIT causes the VM to leak
memory.
Lastly, what kind of JDBC driver are you using, is it
a type IV driver or does it have some native code in
it (ie, type III or type II driver). If it is not type
IV, this could be the problem as well.
Note that a non type IV driver will gaurantee that a
cursor obtained in one thread _cannot_ be used in
another thread. Banged our head against a wall with
Oracle's OCI fat drivers on this issue.
--- Michel Szybist <[EMAIL PROTECTED]> wrote:
>
> Hi to all, (and happy new year!)
>
> I am doing torture tests on servlets, because we are
> planning to use Linux +
> Apache + JServ for an innovative international Web
> site we would like to
> open in a couple of months. We need a solid and fast
> platform on which we
> could rely, that's why we wanted Linux, Apache and
> Java. But...
>
> JServ 1.1b1 crashes after less than 12 hours of
> torture-testing a servlet
> that does a JDBC SELECT on an Oracle database
> through the network and some
> regex (gnu.regex) on an HTML template file.
>
> My config:
> PII 350/128 Mb RAM on a TR network
> Red Hat Linux 6.0
> Kernel 2.2.5-15 built for 686
> glibc-2.1.2
> Apache 1.3.9
> JServ 1.1b1
> JSDK 2.0 from SUN
> JDK 1.2.2 RC3 from blackdown.org
>
> The tests:
> Test 1: two perl scripts do 100 GET requests on the
> servlet (forking 10
> times, each child doing 10 requests). This is done
> as an infinite loop. This
> results in doing 75000 requests in 4 hours.
> Test 2: two perl scripts do 200 GET requests on the
> servlet (forking 10
> times, each child doing 20 requests).This is done as
> a cron job, 50 times an
> hour. This results in doing 10000 requests in 1
> hour.
>
> The first of the 'java' processes (when ps aux)
> takes about 95% of CPU, the
> other about 0%. No get HTTP request succeed on any
> of our servlets. Simple
> HTTP get requests succeed on regular HTML files.
> (Apache still listening and
> serving, but JServ crashed)
>
> I have the following messages in mod_jserv.log
> (repeated several times):
> ...
> [04/01/2000 12:02:32:369] (EMERGENCY) ajp12: can not
> connect to host
> 127.0.0.1:8007
> [04/01/2000 12:02:32:388] (EMERGENCY) ajp12:
> connection fail
> [04/01/2000 12:02:32:388] (ERROR) an error returned
> handling request via
> protocol "ajpv12"
> ...
>
> In access_log :
> 3399 is the size of the HTML output sent to the
> browser. Suddenly, Apache
> returns nothing :
> ...
> 127.0.0.1 - - [04/Jan/2000:04:51:35 +0100] "GET
> /michel/servlets/jdbc/
> HTTP/1.0" 200 3399 "lwp-trivial/1.32"
> 127.0.0.1 - - [04/Jan/2000:04:56:36 +0100] "GET
> /michel/servlets/jdbc/
> HTTP/1.0" 200 - "lwp-trivial/1.32"
> ...
> HTTP 200 and suddenly HTTP 500 :
> ...
> 127.0.0.1 - - [04/Jan/2000:12:02:29 +0100] "GET
> /michel/servlets/jdbc/
> HTTP/1.0" 200 - "lwp-trivial/1.32"
> 127.0.0.1 - - [04/Jan/2000:12:02:32 +0100] "GET
> /michel/servlets/jdbc/
> HTTP/1.0" 500 647 "lwp-trivial/1.32"
> ...
>
> I launch JServ separetly with the following script:
>
> #!/bin/sh
>
> jsdk=/usr/local/JSDK2.0/lib/jsdk.jar
> jserv=/usr/local/apache/libexec/ApacheJServ.jar
> props=/usr/local/apache/conf/jserv/jserv.properties
> log=/usr/local/apache/logs/mod_jserv.log
>
>
classes=.:/home/michel/servlets/lib/classes111.zip:$jsdk:$jserv
>
> THREADS_FLAG=native
> export THREADS_FLAG
>
> date >> $log
>
> /usr/local/jdk1.2.2/bin/java -Xms50m -Xmx60m
> -classpath $classes
> org.apache.jserv.JServ $props >> $log
>
>
> - limitting the heap size could be the cause ?
> - LAN (TCP/IP) problems could be the cause ?
> - nb of process limit ?
> - nb of sockets ?
> - JDK or JServ problem ? (1.1b3 could solve it ?)
>
>
> Thank you for any help or advice,
> and once again, may this year 2000 make your wishes
> become a reality.
>
> Michel.
>
>
> --
> Michel Szybist
> Technologies Appliqu�es et Internet
> STIME - Groupement des Mousquetaires
> [EMAIL PROTECTED]
> T�l: +33 1 4148 3231
>
>
=====
# Nick Bauman
# Technical Programmer
# http://webhelp.com
# real people, real answers, real time
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://messenger.yahoo.com
--
--------------------------------------------------------------
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]
