JMX.mbean.unregistered - Stopping Coyote
I'm trying to figure out why my apache2/tomcat5.5 combo isn't working any longer since some update I did on my debian 5.0.6 machine. I have three connetors on port 8080, 8081 and 8082 between apache2 and tomcat5.5 to serve some VirtualHosts. None of the Vhosts is working (they are all giving an empty page in the browser, no code and the apache log shows an error 400 (which should be redirected and rewritten withing the Virtual Hosts sections). I enabled log4j logging and I'm seeing in the log: DEBUG main org.apache.catalina.connector.MapperListener - Handle Catalina:type=GlobalRequestProcessor,name=http-8080 type : JMX.mbean.unregistered DEBUG main org.apache.catalina.connector.MapperListener - Handle Catalina:type=GlobalRequestProcessor,name=http-8080 type : JMX.mbean.unregistered DEBUG main org.apache.catalina.connector.MapperListener - Handle Catalina:type=Mapper,port=8081 type : JMX.mbean.unregistered DEBUG main org.apache.catalina.connector.MapperListener - Handle Catalina:type=Mapper,port=8081 type : JMX.mbean.unregistered DEBUG main org.apache.catalina.connector.MapperListener - Handle Catalina:type=ProtocolHandler,port=8081 type : JMX.mbean.unregistered DEBUG main org.apache.catalina.connector.MapperListener - Handle Catalina:type=ProtocolHandler,port=8081 type : JMX.mbean.unregistered INFO main org.apache.coyote.http11.Http11BaseProtocol - Stopping Coyote HTTP/1.1 on http-8081 DEBUG http-8081-Processor1 org.apache.tomcat.util.threads.ThreadPool - Terminate DEBUG http-8081-Processor2 org.apache.tomcat.util.threads.ThreadPool - Terminate DEBUG http-8081-Processor3 org.apache.tomcat.util.threads.ThreadPool - Terminate I'm not sure whether this is the cause of the malfunction but it was the only thing I could pinpoint. -- Christoph P.U. Kukulies - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JMX.mbean.unregistered - Stopping Coyote
Christoph Kukulies wrote: I'm trying to figure out why my apache2/tomcat5.5 combo isn't working any longer since some update I did on my debian 5.0.6 machine. What did you update ? What kind of connector is supposed to be used between Apache httpd and Tomcat ? (mod_proxy_http, mod_proxy_ajp, mod_jk ?) Where are the virtual Hosts defined ? in the httpd or the tomcat configuration, or both ? I have three connetors on port 8080, 8081 and 8082 between apache2 and tomcat5.5 to serve some VirtualHosts. None of the Vhosts is working (they are all giving an empty page in the browser, no code and the apache log shows an error 400 (which should be redirected and rewritten withing the Virtual Hosts sections). I enabled log4j logging and I'm seeing in the log: DEBUG main org.apache.catalina.connector.MapperListener - Handle Catalina:type=GlobalRequestProcessor,name=http-8080 type : JMX.mbean.unregistered DEBUG main org.apache.catalina.connector.MapperListener - Handle Catalina:type=GlobalRequestProcessor,name=http-8080 type : JMX.mbean.unregistered DEBUG main org.apache.catalina.connector.MapperListener - Handle Catalina:type=Mapper,port=8081 type : JMX.mbean.unregistered DEBUG main org.apache.catalina.connector.MapperListener - Handle Catalina:type=Mapper,port=8081 type : JMX.mbean.unregistered DEBUG main org.apache.catalina.connector.MapperListener - Handle Catalina:type=ProtocolHandler,port=8081 type : JMX.mbean.unregistered DEBUG main org.apache.catalina.connector.MapperListener - Handle Catalina:type=ProtocolHandler,port=8081 type : JMX.mbean.unregistered INFO main org.apache.coyote.http11.Http11BaseProtocol - Stopping Coyote HTTP/1.1 on http-8081 DEBUG http-8081-Processor1 org.apache.tomcat.util.threads.ThreadPool - Terminate DEBUG http-8081-Processor2 org.apache.tomcat.util.threads.ThreadPool - Terminate DEBUG http-8081-Processor3 org.apache.tomcat.util.threads.ThreadPool - Terminate I'm not sure whether this is the cause of the malfunction but it was the only thing I could pinpoint. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: JMX.mbean.unregistered - Stopping Coyote
Am 07.12.2010 12:01, schrieb André Warnier:
Christoph Kukulies wrote:
I'm trying to figure out why my apache2/tomcat5.5 combo isn't working
any longer since some update
I did on my debian 5.0.6 machine.
What did you update ?
It's a couple of months back and I did some apt-get update/upgrade over
all and after that my tomcat5.5 was screwed.
I also wonder why this jmx stuff was there (I removed the jmx related
jars from the bin and lib directory
and now the listeners keep up running.
The VirtualHosts are defined in the httpd.conf on the apache side and
I'm using direct connectors there (is that mod_proxy_http?).
VirtualHost *
ServerName www.mysite3.de
DocumentRoot /usr/share/tomcat5.5-webapps/ROOT/
ScriptAlias /Perl/ /home/www/mysite3.de/Perl/
Directory /
Options FollowSymLinks
AllowOverride None
Allow from all
/Directory
Directory /usr/share/tomcat5.5-webapps/ROOT/
Options FollowSymLinks
AllowOverride None
Allow from all
/Directory
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
ServerSignature Off
SetEnvIf Request_URI \/opencms\/* redirect
# Redirect all request to non-existing file in the export directory
# to OpenCms which will generate the files on the fly
RewriteEngine on
# Redirection for static export
RewriteCond %{REQUEST_URI} ^/export/(.*) [NC]
RewriteCond
%{DOCUMENT_ROOT}%{REQUEST_FILENAME} !-f
RewriteCond
%{DOCUMENT_ROOT}%{REQUEST_FILENAME}/index_export.html !-f
RewriteRule .*
http://127.0.0.1:8082/opencms/handle404?exporturi=%{REQUEST_URI}%{QUERY_STRING}
[P]
# Redirect all 404 errors to OpenCms
ErrorDocument 404 /system/shared/handle404.html
# Basic proxy rules
ProxyPreserveHost On
RedirectPermanent /opencms/ http://www.mysite3.de/
ProxyPass /opencms/ !
ProxyPass /resources/ !
ProxyPass /export/!
ProxyPass /skins/ !
ProxyPass /syscp/ !
ProxyPass / http://127.0.0.1:8082/opencms/
ProxyPassReverse / http://127.0.0.1:8082/opencms/
ProxyPass /webdav/ http://127.0.0.1:8082/webdav/
ProxyPassReverse /webdav http://127.0.0.1:8082/webdav/
/VirtualHost
server.xml:
!-- Define a non-SSL HTTP/1.1 Connector on port 8180 --
Connector port=8080 maxHttpHeaderSize=8192
proxyName=cms.mysite1.de
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
enableLookups=false redirectPort=8443 acceptCount=100
connectionTimeout=2 disableUploadTimeout=true /
Connector port=8081 maxHttpHeaderSize=8192
proxyName=www.mysite2.de
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
enableLookups=false redirectPort=8443 acceptCount=100
connectionTimeout=2 disableUploadTimeout=true /
Connector port=8082 maxHttpHeaderSize=8192
proxyName=www.mysite3.de
maxThreads=150 minSpareThreads=25 maxSpareThreads=75
enableLookups=false redirectPort=8443 acceptCount=100
/
What kind of connector is supposed to be used between Apache httpd and
Tomcat ? (mod_proxy_http, mod_proxy_ajp, mod_jk ?)
Where are the virtual Hosts defined ? in the httpd or the tomcat
configuration, or both ?
See above.
I'm using the ROOT directory for the OpenCMS content management system.
I'm wondering why http://www.mysite3.de:808[012]/admin is available at all.
maybe the admin package gets into the way?
I have three connetors on port 8080, 8081 and 8082 between apache2
and tomcat5.5 to serve some
VirtualHosts. None of the Vhosts is working (they are all giving an
empty page in the browser, no code
and the apache log shows an error 400 (which should be redirected and
rewritten withing the Virtual Hosts sections).
I enabled log4j logging and I'm seeing in the log:
DEBUG main org.apache.catalina.connector.MapperListener - Handle
Catalina:type=GlobalRequestProcessor,name=http-8080 type :
JMX.mbean.unregistered
DEBUG main org.apache.catalina.connector.MapperListener - Handle
Catalina:type=GlobalRequestProcessor,name=http-8080 type :
JMX.mbean.unregistered
DEBUG main org.apache.catalina.connector.MapperListener - Handle
Catalina:type=Mapper,port=8081 type : JMX.mbean.unregistered
DEBUG main org.apache.catalina.connector.MapperListener - Handle
Catalina:type=Mapper,port=8081 type : JMX.mbean.unregistered
DEBUG main org.apache.catalina.connector.MapperListener - Handle
Catalina:type=ProtocolHandler,port=8081 type : JMX.mbean.unregistered
DEBUG main org.apache.catalina.connector.MapperListener - Handle
Catalina:type=ProtocolHandler,port=8081 type : JMX.mbean.unregistered
INFO main org.apache.coyote.http11.Http11BaseProtocol - Stopping
Coyote HTTP/1.1 on http-8081
DEBUG http-8081-Processor1
Re: JMX.mbean.unregistered - Stopping Coyote
On 12/7/10 11:22 AM, Christoph Kukulies wrote: I also wonder why this jmx stuff was there (I removed the jmx related jars from the bin and lib directory and now the listeners keep up running. Which jars did you remove? p 0x62590808.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
