Trouble getting consistent PID of tomcat server from ps
Hello all,
I am working on a script to automate the process of restarting some tomcat servers. The versions of tomcat are pretty old and it often happens that they don't shut down gracefully and the PID needs to be manually killed. I am having a bear of a time getting a consistent PID from ps though, since sometimes other java processes show up and I get more than one PID from
(Xms is one of the values from the PID that I thought was unique to the server process, but apparently not since it double matches periodically.)
I have tried all kinds of way to trick it out, but when I run a test like
I always wind up getting kicked out of the loop b/c ps returned more than one value.
Any suggestions of things I can try to get the right value 100% of the time?
hey there
we cant seem to get jsp to load pages properly on linux running tomcat 4 server. everytime we run .jsp files, the source code comes up instead of the actual file contents. any suggestions??
cheers
mile1982 (1 Reply)
Hi all,
I Installed Tomcat in an remote linux server (/usr/tomcat)and start service, using ./startup.sh (and tried with ./catalina.sh too).
//----------------------------------------------------------------//
# ./startup.sh
Using CATALINA_BASE: /usr/tomcat/apache-tomcat-6.0.16/
Using... (1 Reply)
hi,
I need a command that restart the tomcat server.
for example for restart the tomcat i am using following command, /etc/init.d/tomcat restart ..but sometimes is not working...might be i want to use java code access this peace of script.
like using the grep and ps commands can i use?... (2 Replies)
Hello,
I have a socket programming code to do chatting(both server and client).
But this is limited to a single machines with multi users.
But my target is to perform chat operation on multiple IP addresses in a given LAN in college.
Can you please tell me if I can use TOMCAT as my server to... (3 Replies)
I do not know the difference between the apache-http and the apche-Tomcat.Is they are differentiated on their version or on their features.:confused: (2 Replies)
Trying to get tomcat 5.5.28 downloaded from apache.org running on a stock Solaris 10 zone. No matter what, I cannot get it to start. I've tried setting my JAVA_home to a jre 1.6, didn't work. Didn't work with the stock Java 1.4.2 install. What am I missing?
-bash-3.00# sh... (4 Replies)
Hi,
I have installed
following software on my linux machine.
Is there anything else required to run jsp pages on linux machine?
Please Help
Here are some details that might be helpful.
# lsb_release -a
LSB Version: ... (3 Replies)
Hello everyone,
I have a small expect script as follows;
#!/usr/bin/expect -f
set force_conservative 0 ;# set to 1 to force conservative mode even if
;# script wasn't run conservatively originally
if {$force_conservative} {
set send_slow {1 .1}
proc send {ignore arg}... (1 Reply)
Tomcat stops logging intermittently for brief intervals of time like for 5 or 6 secs
I wish to monitor if my Tomcat process gets stuck, hung or even shutdown or remains healthy at the time i see the problem of no logging.
Can you please let me know how can i monitor Tomcat Application... (10 Replies)
Hi,
I have been assigned a task to build a server with these requirements :
> has multiple tomcats running under the same apache.
> tomcat & jdk has to be binded with apache.
> latest openssl with all necesarry "mod" to bind with apache & tomcat.
I am fairly new to... (1 Reply)
Discussion started by: anaigini45
1 Replies
LEARN ABOUT OPENDARWIN
shlock
SHLOCK(1) BSD General Commands Manual SHLOCK(1)NAME
shlock -- create or verify a lock file for shell scripts
SYNOPSIS
shlock -f lockfile [-p PID] [-u] [-v]
DESCRIPTION
The shlock command can create or verify a lock file on behalf of a shell or other script program. When it attempts to create a lock file, if
one already exists, shlock verifies that it is or is not valid. If valid, shlock will exit with a non-zero exit code. If invalid, shlock
will remove the lock file, and create a new one.
shlock uses the rename(2) system call to make the final target lock file, which is an atomic operation (i.e. "dot locking", so named for this
mechanism's original use for locking system mailboxes). It puts the process ID ("PID") from the command line into the requested lock file.
shlock verifies that an extant lock file is still valid by using kill(2) with a zero signal to check for the existence of the process that
holds the lock.
The -f argument with lockfile is always required.
The -p option with PID is given when the program is to create a lock file; when absent, shlock will simply check for the validity of the lock
file.
The -u option causes shlock to read and write the PID as a binary pid_t, instead of as ASCII, to be compatible with the locks created by
UUCP.
The -v option causes shlock to be verbose about what it is doing.
RETURN VALUES
A zero exit code indicates a valid lock file.
EXAMPLES
BOURNE SHELL
#!/bin/sh
lckfile=/tmp/foo.lock
if shlock -f ${lckfile} -p $$
then
# do what required the lock
rm ${lckfile}
else
echo Lock ${lckfile} already held by `cat ${lckfile}`
fi
C SHELL
#!/bin/csh -f
set lckfile=/tmp/foo.lock
shlock -f ${lckfile} -p $$
if ($status == 0) then
# do what required the lock
rm ${lckfile}
else
echo Lock ${lckfile} already held by `cat ${lckfile}`
endif
The examples assume that the filesystem where the lock file is to be created is writeable by the user, and has space available.
HISTORY
shlock was written for the first Network News Transfer Protocol (NNTP) software distribution, released in March 1986. The algorithm was sug-
gested by Peter Honeyman, from work he did on HoneyDanBer UUCP.
AUTHOR
Erik E. Fair <fair@clock.org>
BUGS
Does not work on NFS or other network filesystem on different systems because the disparate systems have disjoint PID spaces.
Cannot handle the case where a lock file was not deleted, the process that created it has exited, and the system has created a new process
with the same PID as in the dead lock file. The lock file will appear to be valid even though the process is unrelated to the one that cre-
ated the lock in the first place. Always remove your lock files after you're done.
BSD June 29, 1997 BSD