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


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

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

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

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

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

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


desc
@null
@


1.6
log
@null
@
text
@IDependOn-Set: 1
IDependOn-Set: 2
IDependOn-Set: 264
IDependOn-Set: 274
IDependOn-Set: 278
IDependOn-Set: 7
LastModifiedSecs: 933965780
Parent: 7
SequenceNumber: 2
Title: lingering java processes after reload
Part: 0
Author-Set: jon@@working-dogs.com
HideAttributions: 1
LastModifiedSecs: 933965780
Type: monospaced
Lines: 37


----------
From: "Craig McClanahan" <cmcclanahan@@mytownnet.com>
To: Java Apache <java-apache@@list.working-dogs.com>
Subject: Re: lingering java processes after reload
Date: Fri, Aug 6, 1999, 2:36 AM

Chris McCarthy wrote:

> Every time I reload my servlets (copy a new class and run the servlet)
> I get a new java process lingering around. The process is doing nothing, and
> as such isn't causing me a problem. However, after a day of development
> I have about 70 java processes on the system. If I kill one of them off, they
> all die and jserv starts up the initial ones again.
>
> Is this normal, a bug or a configuration error ?
>
> I'm running RedHat 6.0, Apache 1.3.6 and JServ 1.0
>
> ..Chris.
>

If you are running Linux with native threads, the "ps" command lies to you.  Each
of those "processes" is actually a thread in the existing JVM. To prove it, just
do a normal shutdown and they will all disappear.  In fact, the number of new
threads per reload depends on your configuration parameters -- some people have
reported seeing five or six new threads per iteration.

So why do you get new threads all the time?  I suspect there's a problem in the
JVM, garbage collecting old  thread occurrences.

Note that the multiple occurrences of httpd processes are in fact processes,
because Apache 1.3.x is not multi-threaded.

Craig McClanahan

EndPart: 0
@


1.5
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 933965763
d9 1
a9 1
SequenceNumber: 1
d11 44
@


1.4
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 933871377
d9 2
a10 2
SequenceNumber: 0
Title: New Item
@


1.3
log
@null
@
text
@d5 1
a5 1
IDependOn-Set: 275
@


1.2
log
@null
@
text
@d5 1
@


1.1
log
@null
@
text
@d3 1
@
