FYI - From TC bugzilla. So I added -pidfile jsvc.pid to my execution
and am not killing the jsvc process not the JVM itself.
--- Additional Comments From [EMAIL PROTECTED] 2005-08-02 03:51 ---
This is by design. With jsvc, you are supposed to shutdown Tomcat by:
kill -TERM `cat
I've never had TC bind itself to 127.0.0.1:8005 to allow correct
shutdown to occur. I've always had to kill the TC JVM.
I use JSVC to be able to get a non-root userid. Does this affect how
the shutdown port works ?
My startup command line:
./bin/jsvc -Djava.endorsed.dirs=./common
From: Darryl L. Miles [mailto:[EMAIL PROTECTED]
Subject: TC5.5.9 Linux - shutdown port 8005 not bound BUG?
I've never had TC bind itself to 127.0.0.1:8005 to allow correct
shutdown to occur.
[...]
$ netstat -tanp | grep 80
tcp0 0 :::127.0.0.1:8009
Peter Crowther wrote:
From: Darryl L. Miles [mailto:[EMAIL PROTECTED]
Subject: TC5.5.9 Linux - shutdown port 8005 not bound BUG?
I've never had TC bind itself to 127.0.0.1:8005 to allow correct
shutdown to occur.
[...]
$ netstat -tanp | grep 80
tcp0 0 :::127.0.0.1
From: Darryl L. Miles [mailto:[EMAIL PROTECTED]
Sorry yes... 8009 is the apj13 port (was figuring you'd guess).
Doh. My bad - I use Tomcat directly, not via a front-end, so missed
that one. Sorry Darryl (and anyone reading this thread in the
archives).
My apache is using it locally I have
'
Subject: RE: Shutdown port
Hey!
I had a question! Can you shutdown the machine by typing
http://localhost:8005 in the browser?
I thought this was disabled in the Tomcat version 4 onwards?
Regards
Rajaneesh
-Original Message-
From: Ben Ricker [mailto:[EMAIL PROTECTED]
Sent: Thursday
Is there a way to remove the shutdown port on a server ? I tried
pulling the port=8005 option out, but it still listens on that port
and I'm able to shut it down.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
From what I understand from other postings, no. However, the shutdown
port is bound to the localhost interface so only a connection from
127.0.0.1 will work. Joe Schmoe client out in internet land can't
shutdown your tomcat service.
--David
Frank Parato wrote:
Is there a way to remove
-Original Message-
From: Frank Parato [mailto:[EMAIL PROTECTED]
Sent: 12 January 2005 12:55
To: Tomcat Users List
Subject: Shutdown port
Is there a way to remove the shutdown port on a server ? I tried
pulling the port=8005 option out, but it still listens on that port
and I'm able to shut
You're right. Thanks!
-Original Message-
From: David Smith [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 12, 2005 8:06 AM
To: Tomcat Users List
Subject: Re: Shutdown port
From what I understand from other postings, no. However, the shutdown
port is bound to the localhost
the shutdown port on a server ? I tried
pulling the port=8005 option out, but it still listens on that port
and I'm able to shut it down.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
To: Tomcat Users List
Subject: Re: Shutdown port
For an extra bit of security,replace SHUTDOWN with some sort of long,
random string and then lock down the server.xml to 640. Someone who
gains, or already has access to the box can shut it down the other way.
Ben Ricker
On Jan 12, 2005, at 6:55 AM
Hi,
and thanks for your help!
unfortunately my moderate skills in programming do not allow a customized solution, so
I will choose a separate shutdown port for each of my Tomcats :-/
Have a nice day,
Sascha
On Tuesday, October 12, 2004, at 05:12PM, Shapira, Yoav [EMAIL PROTECTED] wrote:
Hi
Hi,
is it possible to bind the shutdown port to one single IP address?
I do have a clustered environment and running different virtual hosts on the same
physical host. Tomcat now binds the shutdown port always to localhost.8005 and with
this localhost, all virtual hosts are included. But I just
will have a configurable
shutdown address.
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: Sascha Vital [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 12, 2004 11:07 AM
To: [EMAIL PROTECTED]
Subject: how to bind the shutdown port to one single IP address
Hi
Hello All
I have successfully installed TC 4.0.6 on Win XP Pro and it starts fine
at boot time.
But it is NOT listening on the shutdown port and thus of course I can
not restart or stop the server and have to End Process and then start
it using the script.
The shutdown port in the server.xml
Hi
I have successfully installed TC 4.0.6 on Win XP Pro and it starts fine at
boot time.
Is there any reason, you did that?
4.0.6 is VERY old. Try 5.0.x at least.
Regards,
Steffen
smime.p7s
Description: S/MIME cryptographic signature
I have worked with the 5.0.x but my client uses 4.0.6 and i wanted to
have the similar env on my end to do some work off site.
Steffen Heil wrote:
Hi
I have successfully installed TC 4.0.6 on Win XP Pro and it starts fine at
boot time.
Is there any reason, you did that?
4.0.6 is VERY
Nottrott [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 9:50 PM
To: [EMAIL PROTECTED]
Subject: information on tomcat shutdown port / mechanism
Hello,
Can somebody out there point me to a place with explanations of the
Tomcat
shutdown mechanism and how it relates to the shutdown port
(default
Hello,
Can somebody out there point me to a place with explanations of the Tomcat
shutdown mechanism and how it relates to the shutdown port
(default
Server port=8005 shutdown=SHUTDOWN debug=0
)
I'm having some trouble shutting down tomcat normally after changing that
port, and I'm looking
Hi,
The problem we face is Tomcat started but shutdown port 8005 not listening.
The problem is further explained in little detail below.
We use port 8180 for http , port 8005 is used for shutdown.
For accessing web pages from tomcat by http port 8180(http) and
8005(shutdown) both should
Howdy,
The shutdown port starts even before the connector port(s) so it's not
an issue of the shutdown port starting slowly.
The shutdown port by default only listens to connections from the local
host. So you should have a line like localhost.8005 ... LISTEN in your
netstat output. Can you
Hi all,
I am experiencing difficulties with port 8005. It crashes
with a BindException after trying to start it.
OS: SunOS 5.9
www2# java -showversion
java version 1.4.0_03
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0_03-b04)
Java
: Juanpablo Lajud [mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2003 2:12 PM
To: [EMAIL PROTECTED]
Subject: BindException :: Shutdown Port 8005 :: Solaris 5.9
Hi all,
I am experiencing difficulties with port 8005. It crashes
with a BindException after trying to start it.
OS
signal?
2) What's the appropriate thing to grep for ?
-Original Message-
From: Juanpablo Lajud [mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2003 2:12 PM
To: [EMAIL PROTECTED]
Subject: BindException :: Shutdown Port 8005 :: Solaris 5.9
Hi all,
I am experiencing
'
Asunto: RE: BindException :: Shutdown Port 8005 :: Solaris 5.9
Thinking about that a bit more.. if it's 3.3.1a that works, then THAT
maybe be the version that is still running... so grep'ing for
[o]rg.apache.catalina.startup.Bootstrap start
won't work, if this is indeed the problem.
more
PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: disabling shutdown port
Hi folks.
I was wondering how i completely disable the port the tomcat
opens, which can be used to to shutdown tomcat.
I tried changing things in the server entry, but
i didnt help
Hi folks.
I was wondering how i completely disable the port the tomcat
opens, which can be used to to shutdown tomcat.
I tried changing things in the server entry, but
i didnt help.
Ideas?
Regards
Taisto Qvist
IP Solutions
/ ^ ^ \
28 matches
Mail list logo
