----------------------------------------------------------------
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!!!
----------------------------------------------------------------
On Wed, 10 May 2000, Williams, Murray Todd wrote:
> I've gone through the FAQ and the last three weeks of mailing list archives,
> and I've seen one person mention this problem, but no further discussion.
>
> I'm the (unofficial) maintainer of the RPM packages for Xerces, Xalan and
> Cocoon (these RPMs being built on top of the "official" JServ RPM that is
> posted on the java.apache.org web site. For the last few months I noticed
> something a little odd, but I didn't pay much attention. I've finally
> decided to look closer and I'm very concerned.
>
> I tried submitting a bug report on the automated web form, but I've tried on
> two days from two different locations (home and work) and I keep getting and
> error back telling me that all my form inputs are blank, so I guess that
> isn't working. Instead I've copied all the sections down here...
>
> ***Environment:***
> I have this occuring on two platforms: RedHat Linux 6.1 and 6.2 (Intel) and
> on
> LinuxPPC (specifically YellowDog) for the PowerPC. I recompiled the .src.rpm
> file
> on PPC to create the installation rpm. The Java environments include
> Blackdown's
> JDK 1.2.2RC4 on both Intel and PPC, as well as IBM's new JDK1.3 for Intel.
>
> ***Synopsis:***
> A bunch of zombie (defunct) jdk theads and constantly being created and
> destroyed.
I'm not sure I understand what the problem is or why anything you describe
is a problem.
TIME_WAIT is a normal TCP state that things go through during the
shutdown of a TCP connection. There is nothing "stuck" about it and
just because there is a connection in TIME_WAIT doesn't mean there
is some process waiting for it.
jserv's use of threads requires that a new one is created and destroyed
for each request; on Linux, these will show up in a normal ps because
of how Linux threads work.
jserv automatically connects to the JVM to verify that it is up
and running and happy. This is not done if you start the JVM
manually, since then it is your problem to ensure it is running
properly.
This seems to explain everything you see without there being any
"problem".
--
--------------------------------------------------------------
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]
