Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
From: Bernard <bht@actrix.gen.nz>
To: commons-dev@jakarta.apache.org
Subject: jsvc on Linux: multiple instances possible, why -pidfile?
Date: Tue, 15 Feb 2005 00:33:17 +1300
Message-ID: <i121119uk7ui9bno55ru20lcndi3aac8re@4ax.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi,


I created multiple jsvc instances that did not die.
That happens with the adapted Tomcat5.sh supplied with the Tomcat 5.5
distribution.

That's a problem.

I would appreciate some help in understanding the logic of the pid
file.

This is my view of things; please correct me and help me if I am
wrong:

If, as it is presently the case, jsvc creates a pid file, then it must
not be possible for jsvc to launch a second copy of a service.

jsvc should however be able to briefly run only itself as multiple
instances - it must be allowed to do so in order to check the pid
file. It would not be reliable to pass this responsibility to the OS.

So any jsvc copy on top of the first should exit with an error
condition, and it should not attempt to start the jvm with the server.

If jsvc is NOT designed to block multiple service instances, then it
must not write the PID file. In that case it would be the
responsibility of the script to write the pid file and block multiple
service instances.

What to do?

Many thanks,

Bernard


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org