head	1.8;
access;
symbols;
locks
	nobody:1.8; strict;
comment	@# @;


1.8
date	99.10.01.20.59.31;	author nobody;	state Exp;
branches;
next	1.7;

1.7
date	99.09.13.18.30.33;	author nobody;	state Exp;
branches;
next	1.6;

1.6
date	99.09.13.18.30.17;	author nobody;	state Exp;
branches;
next	1.5;

1.5
date	99.09.13.18.30.01;	author nobody;	state Exp;
branches;
next	1.4;

1.4
date	99.09.13.18.29.45;	author nobody;	state Exp;
branches;
next	1.3;

1.3
date	99.09.13.18.29.11;	author nobody;	state Exp;
branches;
next	1.2;

1.2
date	99.09.13.18.28.34;	author nobody;	state Exp;
branches;
next	1.1;

1.1
date	99.09.13.18.28.06;	author nobody;	state Exp;
branches;
next	;


desc
@null
@


1.8
log
@null
@
text
@IDependOn-Set: 1
IDependOn-Set: 183
IDependOn-Set: 2
IDependOn-Set: 230
IDependOn-Set: 300
LastModifiedSecs: 938811571
Parent: 2
SequenceNumber: 6
Title: Positive Experiences
Part: 0
Author-Set: jon@@working-dogs.com
HideAttributions: 1
LastModifiedSecs: 937247384
Type: 
Lines: 1
This section deals with positive experiences with Apache JServ. Yes, it actually does work.
EndPart: 0
Part: 1
Author-Set: jon@@working-dogs.com
HideAttributions: 1
LastModifiedSecs: 937247433
Type: monospaced
Lines: 48
----------
From: Jorgen Skjaanes <jorgen@@gulesider.no>
To: Java Apache Users <java-apache-users@@list.working-dogs.com>
Subject: Re: JServ timing out...
Date: Mon, Sep 13, 1999, 9:17 AM

On Mon, 13 Sep 1999, Priatel, Mark (ott) wrote:

> It seems that if I leave JServ alone for a couple hours (overnight) and then
> try in the morning to access one of my servlets, it just hangs.   In fact,
> every servlet hangs...The only thing I can to do fix this, is to restart
> Apache...

Anything in the logs?

> (Actually, while writing this I just restarted apache to fix the problem,
> and it told me httpd wasn't running...hmmm)

We've had this problem with servlets hanging a few times and it was always a
bug in our own servlets/classes that caused it. It usually had to do with bug's
in the code dealing with the pool of DB connections. Are your servlets
connecting to a DB by any chance?

Of course when we couldn't find the bug in a few hours we always started to 
blame either jserv or the jvm (the same as yours), and one time we got so 
desperate that we started to look at jrun and other jvms since we were
sure this was the only way out. But of course, it turned out to be a bug
in a class that forgot to close DB-connections in some obscure cases.

Now we are extremely happy with apache jserv. It runs for days without any
crash or memory leak what so ever. We only restart it when we are
updating the servlets. And we're a quite busy site (The Norwegian Yellow
Pages) serving almost 200 _servlets_ each minute at peak times. This on a
single processor P-II 333, 384MB of memory, RH 5.2. The load never reaches 1,
even at peak times.

> Anyhow, am I missing some simple configuration option?  Is there some way to
> have a cron job that checks periodically for Apache, and restarts it if it's
> down?

That's a simple thing to write, but I think you have a bug in your own servlet/
java code and you should fix that instead of hiding it with constant restarts.
Try keeping an eye on top and see if anything is eating memory. And try logging
as much as possible and see if you can find out anything that way.

-- 
Jorgen Skjaanes
http://www.gulesider.no
EndPart: 1
Part: 2
Author-Set: huele@@ww3.com
HideAttributions: 1
LastModifiedSecs: 938811571
Type: monospaced
Lines: 1
How do you measure the performance of Jserv?
EndPart: 2
@


1.7
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 937247433
d8 1
a8 1
SequenceNumber: 5
d73 8
@


1.6
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 937247417
d8 1
a8 1
SequenceNumber: 4
d21 2
a22 1
LastModifiedSecs: 937247416
@


1.5
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 937247400
d8 1
a8 1
SequenceNumber: 3
d18 54
@


1.4
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 937247384
d8 1
a8 1
SequenceNumber: 2
d14 1
a17 9
Part: 1
HideAttributions: 1
Type: directory
Lines: 4
Subcategories:


Answers in this category:
EndPart: 1
@


1.3
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 937247351
d8 1
a8 1
SequenceNumber: 1
d11 7
d25 1
a25 1
EndPart: 0
@


1.2
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 937247284
d8 2
a9 2
SequenceNumber: 0
Title: New Item
@


1.1
log
@null
@
text
@d2 1
d4 1
@
