Re: TC5.5.9 Linux - shutdown port 8005 not bound BUG?
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 $PIDFILE` As a result, jsvc doesn't tell Tomcat to listen on port 8005. -- Darryl L. Miles - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TC5.5.9 Linux - shutdown port 8005 not bound BUG?
> 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 added > address="127.0.0.1" for ajp13 > so its not exposed externally. Makes sense. I'll crawl back into my hole now. - Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: TC5.5.9 Linux - shutdown port 8005 not bound BUG?
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:8009 :::*LISTEN 4621/jsvc.exec There it is, on 8009 not 8005. Should I file this as a bug ? Depends - have you changed your server.xml at all? Sorry yes... 8009 is the apj13 port (was figuring you'd guess). My apache is using it locally I have added address="127.0.0.1" for ajp13 so its not exposed externally. -- Darryl L. Miles - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: TC5.5.9 Linux - shutdown port 8005 not bound BUG?
> 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 > :::*LISTEN 4621/jsvc.exec There it is, on 8009 not 8005. > Should I file this as a bug ? Depends - have you changed your server.xml at all? - Peter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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. 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 tcp0 0 :::127.0.0.1:8009 :::*LISTEN 4621/jsvc.exec tcp0 0 :::127.0.0.1:8080 :::*LISTEN 4621/jsvc.exec Should I file this as a bug ? -- Darryl L. Miles - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]