tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 35967] New: - shutdown port 8005 not bound
Date Tue, 02 Aug 2005 01:17:42 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35967>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35967

           Summary: shutdown port 8005 not bound
           Product: Tomcat 5
           Version: 5.5.9
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: darryl@darrylmiles.org


>From my tomcat-users-list posting:

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/endorsed -classpath
:/opt/jakarta-tomcat-5.5.9/bin/bootstrap.jar:/opt/jakarta-tomcat-5.5.9/bin/commons-logging-api.jar
-Dcatalina.base=/opt/jakarta-tomcat-5.5.9
-Dcatalina.home=/opt/jakarta-tomcat-5.5.9
-Djava.io.tmpdir=/opt/jakarta-tomcat-5.5.9/temp -outfile ./logs/catalina.out
-errfile ./logs/catalina.err -user jakarta -Xmx2048M -Xms512M
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
org.apache.catalina.startup.Bootstrap start

$ netstat -tanp | grep 80
tcp        0      0 ::ffff:127.0.0.1:8009       :::*                       
LISTEN      4621/jsvc.exec
tcp        0      0 ::ffff:127.0.0.1:8080       :::*                       
LISTEN      4621/jsvc.exec


8009 is my AJP13, I have added address="127.0.0.1" to the default config, and
8080 is Coyete HTTP listener.

If I start TC up without jsvc, then I can get it to listen on the shutdown port,
why is there a difference.



For interest I run the following to setup jsvc, should you wish to test for
yourself:

# Extracted TC to /opt/jakarta-tomcat-5.5.9
# To run it as java service need to build jsvc
cd /opt/jakarta-tomcat-5.5.9/bin
tar -zxvf jsvc.tar.gz
cd jsvc-src
autoconf
JAVA_HOME="/opt/jdk1.5.0_04"
export JAVA_HOME
sh ./configure
make
cp jsvc ..
cd ..

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message