----------------------------------------------------------------
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!!!
----------------------------------------------------------------
Hi,
thanks everybody for his/her help.
It couldn't find the problem but
helped pointing in the direction of how to
debug.
The problem was not jserv od JDK but the servlet application.
I would like to share this information so others can take care:
The servlet uses javax.mail and had to send mails.
Each mail sending opened a new session object and
each opening costs 22 (!) file descriptors ...
Thats fixed now and the problem disappeared.
>Hi,
>
>thanks for your help, I will investigate further.
>
>>Carsten Heyl wrote:
>>>
>>> Hello JServ supporters,
>>>
>>> I'm using jserv 1.1b3 on Solaris 7, JDK 1.1.7,
>>> Apache 1.3.9.
>>> Apache hosts 2 virtual servers.
>>> JServ hosts 2 zones running gnujsp.
>>>
>>> Problem: The jserv process runs out of file descriptors.
>>>
>>> Taking a look at the list of open files shows that
>>> the jars which are loaded by "repositories="
>>> in zone.properties are opened multiple times
>>> after some servlets or jsp pages are used after a
>>> short time (few minutes).
>>> Then the jserv dies and a new process is started.
>>> Increasing the maximum number of fd's is no solution
>>> and would only help for a few minutes.
>>>
>>are you sure that increasing the number of fd does not solve it ? It has
>>always been _The_ solution. (I experimented it also earlier). (described
>>in the FAQ).Did you try it ?
>
>Yep.
>Got a few minutes when increasing from 64 (default) to 256.
>
>>
>>Also, did you try to use the autoreload false? Checking all the time is
>>CPU & IO expensive, and not really needed on production sites.
>>Does it happen without autoreloading ?
>
>Will check that. On jserv 1.0 it did not change the behaviour, will
>check for 1.1b3.
>And the other tip checking the number of apache connection
>may be interesting, too.
>
>>
>>An alternate solution is playing with 2 load-balanced JServ (only one
>>started). Upgrade the 2nd, then start it, then stop the first one,
>>upgrade then restart (or not).
>
>Upgrade? I don't understand.
>
>>
>>Jean-Luc
>>
>>
>>--
>>--------------------------------------------------------------
>>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]
>>
>>
>
>Ciao,
> Carsten Heyl
>
> Carsten Heyl [EMAIL PROTECTED]
> NADS - Solutions on Nets http://www.nads.de/
> NADS GmbH http://www.pixelboxx.de/
> Hildebrandtstr. 4E Tel.: +49 211 933 02-90
>D-40215 Duesseldorf Fax.: +49 211 933 02-93
>
>
>--
>--------------------------------------------------------------
>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]
>
>
Ciao,
Carsten Heyl
Carsten Heyl [EMAIL PROTECTED]
NADS - Solutions on Nets http://www.nads.de/
NADS GmbH http://www.pixelboxx.de/
Hildebrandtstr. 4E Tel.: +49 211 933 02-90
D-40215 Duesseldorf Fax.: +49 211 933 02-93
--
--------------------------------------------------------------
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]
