Re: Adding the manager app to a Standalone tomcat install
On Mon, May 7, 2012 at 2:57 PM, André Warnier a...@ice-sa.com wrote: Ognjen Blagojevic wrote: Todd, On 4.5.2012 22:01, Todd Seidenberg wrote: xx.x.32.16 - - [04/May/2012:13:59:05 -0600] GET /manager/html HTTP/1.1 404 991 - Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04 Chromium/18.0.1025.151 Chrome/18.0.1025.151 Safari/535.19 xx.x.32.16 - - [04/May/2012:13:59:34 -0600] GET /manager/html HTTP/1.1 404 991 http://cascade:8090/; Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04 Chromium/18.0.1025.151 Chrome/18.0.1025.151 Safari/535.19 Brainstorming... Did you check access permissions for webapps/manager directory and its contents? User running Tomcat must be able to read it. And one more thing to try : - Stop Tomcat - delete all the Tomcat logfiles (before that, save a copy somewhere, for later reference) - delete the directory /usr/local/confluence-4/conf/**Standalone/ and all its content (Tomcat will regenerate it) - start Tomcat and try again to access the manager app - stop Tomcat - paste the full content here, of the logfile which shows Tomcat being started and the applications being deployed, up to the end showing Tomcat being stopped Note: the directory /usr/local/confluence-4/conf/**Standalone/ is named so, instead of the more classic /usr/local/confluence-4/conf/**Catalina/, because in your server.xml, the Engine tag has been modified, compared to the standard Tomcat 6 server.xml. (the name attribute value was changed from Catalina to Standalone). (And maybe this has something to do with the issue here; it may in any case change the way things are being logged) Folks, I've solved this problem. I wound up completely removing the Confluence/tomcat directories, and restoring them from a tar'd backup. Once I did that, i took the following steps: - set autodeploy to 'true' in the server.xml file - modified the tomcat-users.xml file and server.xml file to reflect the use of a tomcat-users.xml file - copied the manager directory (from the apache-tomcat-6.0.32/webapps directory from a fresh untarring of the tomcat package) tot he webapps directory - started tomcat. This is all I needed to do. The manager deployed correctly, and created a manager.xml file in the appropriate place. Not sure how things had gotten corrupted before, but they did - so I punted. It appears to have worked. Thanks for everyone's help. - Todd --**--**- To unsubscribe, e-mail: users-unsubscribe@tomcat.**apache.orgusers-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
Todd, On 4.5.2012 22:01, Todd Seidenberg wrote: xx.x.32.16 - - [04/May/2012:13:59:05 -0600] GET /manager/html HTTP/1.1 404 991 - Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04 Chromium/18.0.1025.151 Chrome/18.0.1025.151 Safari/535.19 xx.x.32.16 - - [04/May/2012:13:59:34 -0600] GET /manager/html HTTP/1.1 404 991 http://cascade:8090/; Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04 Chromium/18.0.1025.151 Chrome/18.0.1025.151 Safari/535.19 Brainstorming... Did you check access permissions for webapps/manager directory and its contents? User running Tomcat must be able to read it. -Ognjen - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
Ognjen Blagojevic wrote: Todd, On 4.5.2012 22:01, Todd Seidenberg wrote: xx.x.32.16 - - [04/May/2012:13:59:05 -0600] GET /manager/html HTTP/1.1 404 991 - Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04 Chromium/18.0.1025.151 Chrome/18.0.1025.151 Safari/535.19 xx.x.32.16 - - [04/May/2012:13:59:34 -0600] GET /manager/html HTTP/1.1 404 991 http://cascade:8090/; Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04 Chromium/18.0.1025.151 Chrome/18.0.1025.151 Safari/535.19 Brainstorming... Did you check access permissions for webapps/manager directory and its contents? User running Tomcat must be able to read it. And one more thing to try : - Stop Tomcat - delete all the Tomcat logfiles (before that, save a copy somewhere, for later reference) - delete the directory /usr/local/confluence-4/conf/Standalone/ and all its content (Tomcat will regenerate it) - start Tomcat and try again to access the manager app - stop Tomcat - paste the full content here, of the logfile which shows Tomcat being started and the applications being deployed, up to the end showing Tomcat being stopped Note: the directory /usr/local/confluence-4/conf/Standalone/ is named so, instead of the more classic /usr/local/confluence-4/conf/Catalina/, because in your server.xml, the Engine tag has been modified, compared to the standard Tomcat 6 server.xml. (the name attribute value was changed from Catalina to Standalone). (And maybe this has something to do with the issue here; it may in any case change the way things are being logged) - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
On 4 May 2012, at 15:18, Todd Seidenberg todd.seidenb...@gmail.com wrote: On Fri, May 4, 2012 at 7:02 AM, Todd Seidenberg todd.seidenb...@gmail.comwrote: On May 3, 2012 5:47 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Todd, On 5/3/12 5:22 PM, Todd Seidenberg wrote: On Thu, May 3, 2012 at 3:03 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Re: Adding the manager app to a Standalone tomcat install I have removed all of the offending stuff from the server.xml but the manager/html still gives me a 404. Just to be sure, exactly what URL are you using to try to access the manager? - Chuck http://hostname:8090/manager/html Grasping at straws: is there an old instance of Tomcat still running and bound to your port? If you enable the AccessLogValve, can you confirm that the request is actually being handled by the instance you are launching? I've never enabled AccessLogValve. Can you give me a quick pointer for turning it on so we can continue debugging? It sounds like something that I should keep in my arsenal of tools. This is truly strange. Agreed. Thanks for taking a look at it. By the way, I should also say that I have now COMPLETELY DISABLED the confluence context in my server.xml file. So it now looks like this: Server port=8000 shutdown=SHUTDOWN Service name=Tomcat-Standalone Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8090 minProcessors=5 maxProcessors=75 enableLookups=false redirectPort=8443 acceptCount=10 connectionTimeout=2 useURIValidationHack=false URIEncoding=UTF-8 / I think it's already been mentioned, but the above Connector definition should be invalid for Tomcat 6. Are you sure there's no extra information in the Tomcat log files that might be useful? p Connector port=8009 protocol=AJP/1.3 redirectPort=8443 / Engine name=Standalone defaultHost=localhost Host name=localhost appBase=webapps unpackWARs=true autoDeploy=true /Host /Engine /Service /Server This is the entirety of it. And of course, the manager still doesn't show up. just to reiterate. - I have the server.xml listed above. - I have grabbed the webapps/manager directory from a full fresh tomcat-6.0.32 install - I can start this standalone tomcat, and the conf/Standalone/localhost/manager.xml is generated. - I do not have an httpd running anywhere. - I STILL get a 404 error when I try to go to http://hostname:8090/manager/html. Anything else I can try? - Thanks, Todd - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
On May 3, 2012 5:47 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Todd, On 5/3/12 5:22 PM, Todd Seidenberg wrote: On Thu, May 3, 2012 at 3:03 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Re: Adding the manager app to a Standalone tomcat install I have removed all of the offending stuff from the server.xml but the manager/html still gives me a 404. Just to be sure, exactly what URL are you using to try to access the manager? - Chuck http://hostname:8090/manager/html Grasping at straws: is there an old instance of Tomcat still running and bound to your port? If you enable the AccessLogValve, can you confirm that the request is actually being handled by the instance you are launching? I've never enabled AccessLogValve. Can you give me a quick pointer for turning it on so we can continue debugging? It sounds like something that I should keep in my arsenal of tools. This is truly strange. Agreed. Thanks for taking a look at it. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+jGN8ACgkQ9CaO5/Lv0PDy9wCdGiyBxh4YA+K4chnAQvp0nhpT N8UAn3gcQebCujSwO5YEVADUoWkrKGel =qT3S -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
On Fri, May 4, 2012 at 7:02 AM, Todd Seidenberg todd.seidenb...@gmail.comwrote: On May 3, 2012 5:47 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Todd, On 5/3/12 5:22 PM, Todd Seidenberg wrote: On Thu, May 3, 2012 at 3:03 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Re: Adding the manager app to a Standalone tomcat install I have removed all of the offending stuff from the server.xml but the manager/html still gives me a 404. Just to be sure, exactly what URL are you using to try to access the manager? - Chuck http://hostname:8090/manager/html Grasping at straws: is there an old instance of Tomcat still running and bound to your port? If you enable the AccessLogValve, can you confirm that the request is actually being handled by the instance you are launching? I've never enabled AccessLogValve. Can you give me a quick pointer for turning it on so we can continue debugging? It sounds like something that I should keep in my arsenal of tools. This is truly strange. Agreed. Thanks for taking a look at it. By the way, I should also say that I have now COMPLETELY DISABLED the confluence context in my server.xml file. So it now looks like this: Server port=8000 shutdown=SHUTDOWN Service name=Tomcat-Standalone Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8090 minProcessors=5 maxProcessors=75 enableLookups=false redirectPort=8443 acceptCount=10 connectionTimeout=2 useURIValidationHack=false URIEncoding=UTF-8 / Connector port=8009 protocol=AJP/1.3 redirectPort=8443 / Engine name=Standalone defaultHost=localhost Host name=localhost appBase=webapps unpackWARs=true autoDeploy=true /Host /Engine /Service /Server This is the entirety of it. And of course, the manager still doesn't show up. just to reiterate. - I have the server.xml listed above. - I have grabbed the webapps/manager directory from a full fresh tomcat-6.0.32 install - I can start this standalone tomcat, and the conf/Standalone/localhost/manager.xml is generated. - I do not have an httpd running anywhere. - I STILL get a 404 error when I try to go to http://hostname:8090/manager/html. Anything else I can try? - Thanks, Todd
Re: Adding the manager app to a Standalone tomcat install
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Todd, On 5/4/12 10:17 AM, Todd Seidenberg wrote: - I have the server.xml listed above. - I have grabbed the webapps/manager directory from a full fresh tomcat-6.0.32 install Where did you put it? In /usr/share/tomcat6/webapps? - I can start this standalone tomcat, and the conf/Standalone/localhost/manager.xml is generated. Okay. Where is conf rooted? - I do not have an httpd running anywhere. - I STILL get a 404 error when I try to go to http://hostname:8090/manager/html. What are catalina.base and catalina.home? Access log documentation can be found here: http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html#Access_Log_Valve - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+j6fEACgkQ9CaO5/Lv0PBCiACgtpjKeLfOi3EoCbc3CIJMh1Pe HA0AoKd6nVnDXZJp8JLdO7246fjqvetI =oLmi -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
On Fri, May 4, 2012 at 8:38 AM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Todd, On 5/4/12 10:17 AM, Todd Seidenberg wrote: - I have the server.xml listed above. - I have grabbed the webapps/manager directory from a full fresh tomcat-6.0.32 install Where did you put it? In /usr/share/tomcat6/webapps? /usr/local/confluence-4/webapps/manager - I can start this standalone tomcat, and the conf/Standalone/localhost/manager.xml is generated. Okay. Where is conf rooted? /usr/local/confluence-4/conf - I do not have an httpd running anywhere. - I STILL get a 404 error when I try to go to http://hostname:8090/manager/html. What are catalina.base and catalina.home? Here's the output of version.sh: - ./version.sh If you encounter issues starting up Confluence Standalone, please see the Installation guide at http://confluence.atlassian.com/display/DOC/Confluence+Installation+Guide Server startup logs are located in /usr/local/confluence-4/logs/catalina.out Using CATALINA_BASE: /usr/local/confluence-4 Using CATALINA_HOME: /usr/local/confluence-4 Using CATALINA_TMPDIR: /usr/local/confluence-4/temp Using JRE_HOME:/usr/local/confluence-4/jre/ Using CLASSPATH: /usr/local/confluence-4/bin/bootstrap.jar Using CATALINA_PID:/usr/local/confluence-4/work/catalina.pid Server version: Apache Tomcat/6.0.32 Server built: February 2 2011 2003 Server number: 6.0.32.0 OS Name:Linux OS Version: 2.6.16.54-0.2.8-default Architecture: i386 JVM Version:1.6.0_26-b03 JVM Vendor: Sun Microsystems Inc. - Access log documentation can be found here: http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html#Access_Log_Valve - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+j6fEACgkQ9CaO5/Lv0PBCiACgtpjKeLfOi3EoCbc3CIJMh1Pe HA0AoKd6nVnDXZJp8JLdO7246fjqvetI =oLmi -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
On Fri, May 4, 2012 at 8:46 AM, Todd Seidenberg todd.seidenb...@gmail.comwrote: On Fri, May 4, 2012 at 8:38 AM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Todd, On 5/4/12 10:17 AM, Todd Seidenberg wrote: - I have the server.xml listed above. - I have grabbed the webapps/manager directory from a full fresh tomcat-6.0.32 install Where did you put it? In /usr/share/tomcat6/webapps? /usr/local/confluence-4/webapps/manager - I can start this standalone tomcat, and the conf/Standalone/localhost/manager.xml is generated. Okay. Where is conf rooted? /usr/local/confluence-4/conf - I do not have an httpd running anywhere. - I STILL get a 404 error when I try to go to http://hostname:8090/manager/html. What are catalina.base and catalina.home? Here's the output of version.sh: - ./version.sh If you encounter issues starting up Confluence Standalone, please see the Installation guide at http://confluence.atlassian.com/display/DOC/Confluence+Installation+Guide Server startup logs are located in /usr/local/confluence-4/logs/catalina.out Using CATALINA_BASE: /usr/local/confluence-4 Using CATALINA_HOME: /usr/local/confluence-4 Using CATALINA_TMPDIR: /usr/local/confluence-4/temp Using JRE_HOME:/usr/local/confluence-4/jre/ Using CLASSPATH: /usr/local/confluence-4/bin/bootstrap.jar Using CATALINA_PID:/usr/local/confluence-4/work/catalina.pid Server version: Apache Tomcat/6.0.32 Server built: February 2 2011 2003 Server number: 6.0.32.0 OS Name:Linux OS Version: 2.6.16.54-0.2.8-default Architecture: i386 JVM Version:1.6.0_26-b03 JVM Vendor: Sun Microsystems Inc. - Access log documentation can be found here: http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html#Access_Log_Valve I've enabled the Access_log_Valve, as listed below: snip Host name=localhost appBase=webapps unpackWARs=true autoDeploy=true Valve className=org.apache.catalina.valves.AccessLogValve directory=logs prefix=tomcat_access_Logs. pattern=combined resolveHosts=false / /snip As expected, I still get the 404 error. Enclosed is the line from the 'tomcat_access_Logs.' file. xx.x.32.16 - - [04/May/2012:13:59:05 -0600] GET /manager/html HTTP/1.1 404 991 - Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04 Chromium/18.0.1025.151 Chrome/18.0.1025.151 Safari/535.19 xx.x.32.16 - - [04/May/2012:13:59:34 -0600] GET /manager/html HTTP/1.1 404 991 http://cascade:8090/; Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04 Chromium/18.0.1025.151 Chrome/18.0.1025.151 Safari/535.19 Thoughts? - Thanks, Todd - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+j6fEACgkQ9CaO5/Lv0PBCiACgtpjKeLfOi3EoCbc3CIJMh1Pe HA0AoKd6nVnDXZJp8JLdO7246fjqvetI =oLmi -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
I have a script in cacti that graphs data from the XML generated by the manager app. I was using this before, with this same application, in a non-standalone mode. I would love to switch back to the previous setup, but cannot because of reasons beyond my control. So if I wanted to drop in a manager app from a complete version of tomcat, will I need a seperate virtual host to run it? Or can I run it's context within the same host thats currently running my standalone app? My previous efforts to do this resulted in a BLANK page when I tried hitting the manager app - so any help would be appreciated. Thoughts? On Wed, May 2, 2012 at 2:46 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Adding the manager app to a Standalone tomcat install I'm trying to use the manager app, so that I can collect performance metrics on our running Standalone Tomcat setup. What kind of performance information do you think the manager webapp will give you? Have you looked at just enabling the AccessLogValve? For real performance data, you might want to look at these: http://moskito.anotheria.net/ http://code.google.com/p/psi-probe/ Is it possible to install the manager app in an install like this? Sure - get a normal Tomcat download for the same version, and copy the manager webapp and its associated manager.xml file over to your installation. You'll likely need to update conf/tomcat-users.xml or whatever authentication mechanism you have employed in order to access the manager. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
On 03/05/2012 14:28, Todd Seidenberg wrote: I have a script in cacti that graphs data from the XML generated by the manager app. I was using this before, with this same application, in a non-standalone mode. I would love to switch back to the previous setup, but cannot because of reasons beyond my control. So if I wanted to drop in a manager app from a complete version of tomcat, will I need a seperate virtual host to run it? Or can I run it's context within the same host thats currently running my standalone app? The manager app must run in the same Host as the apps you want to manage. If you have multiple hosts, then you need multiple Manager app installs. My previous efforts to do this resulted in a BLANK page when I tried hitting the manager app - so any help would be appreciated. Thoughts? .oO( Please don't top post ) p On Wed, May 2, 2012 at 2:46 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Adding the manager app to a Standalone tomcat install I'm trying to use the manager app, so that I can collect performance metrics on our running Standalone Tomcat setup. What kind of performance information do you think the manager webapp will give you? Have you looked at just enabling the AccessLogValve? For real performance data, you might want to look at these: http://moskito.anotheria.net/ http://code.google.com/p/psi-probe/ Is it possible to install the manager app in an install like this? Sure - get a normal Tomcat download for the same version, and copy the manager webapp and its associated manager.xml file over to your installation. You'll likely need to update conf/tomcat-users.xml or whatever authentication mechanism you have employed in order to access the manager. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- [key:62590808] signature.asc Description: OpenPGP digital signature
Re: Adding the manager app to a Standalone tomcat install
2012/5/3 Todd Seidenberg todd.seidenb...@gmail.com: (..) +1 to what Pid wrote. My previous efforts to do this resulted in a BLANK page when I tried hitting the manager app - so any help would be appreciated. Blank page means that there is no ROOT web application deployed on that host. You are likely hitting a wrong URL and there is no default application to display user-friendly 404 page for you. Anyway, a lot depends on how your standalone Tomcat actually operates. If it is close to standard distribution, then changing its configuration should be easy. If it is embedded Tomcat where all configuration is done programmatically by whatever starts is, then you are out of luck, because configuration files will be irrelevant. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
On Thu, May 3, 2012 at 7:37 AM, Konstantin Kolinko knst.koli...@gmail.com
wrote:
2012/5/3 Todd Seidenberg todd.seidenb...@gmail.com:
(..)
+1 to what Pid wrote.
My previous efforts to do this resulted in a BLANK page when I tried
hitting the manager app - so any help would be appreciated.
Blank page means that there is no ROOT web application deployed on that
host.
You are likely hitting a wrong URL and there is no default application
to display user-friendly 404 page for you.
Ok. Thank you for that. I've been able to successfully deploy the ROOT app,
and I get the standard default Tomcat page.
However, when I click on the tomcat manager link, I get:
-
HTTP Status 404 - /manager/html
type Status report
message /manager/html
description The requested resource (/manager/html) is not available.
Apache Tomcat/6.0.32
-
Here's what I've done.
- I've determined the version of Tomcat that my standalone install is using
(6.0.32.)
- I've grabbed a tar.gz of the 6.0.32 standard tomcat and untarred it.
- I've rsync'd the apache-tomcat-6.0.32/webapps/manager directory to my
standalone installation's webapp directory.
- I noted that I had NOTHING in my server.xml for the manager app. (I do
have context clauses in the server.xml for the main app that the standalone
tomcat was bundled with.)
- I made sure that tomcat was killed.
- I then started it up and tailed the log file (Note that the app I'm
running is called 'confluence.' It is running as expected.
--
To run Confluence in the foreground, start the server with
start-confluence.sh -fg
executing using dedicated user: confluence
If you encounter issues starting up Confluence Standalone, please see the
Installation guide at
http://confluence.atlassian.com/display/DOC/Confluence+Installation+Guide
Server startup logs are located in /usr/local/confluence-4/logs/catalina.out
Using CATALINA_BASE: /usr/local/confluence-4
Using CATALINA_HOME: /usr/local/confluence-4
Using CATALINA_TMPDIR: /usr/local/confluence-4/temp
Using JRE_HOME:/usr/local/confluence-4/jre/
Using CLASSPATH: /usr/local/confluence-4/bin/bootstrap.jar
Using CATALINA_PID:/usr/local/confluence-4/work/catalina.pid
SEVERE: The web application [/confluence] created a ThreadLocal with key of
type [com.opensymphony.xwork.ActionContext.ActionContextThreadLocal] (value
[com.opensymphony.xwork.ActionContext$ActionContextThreadLocal@132ba74])
and a value of type [com.opensymphony.xwork.ActionContext] (value
[com.opensymphony.xwork.ActionContext@16f488d]) but failed to remove it
when the web application was stopped. This is very likely to create a
memory leak.
May 3, 2012 9:53:10 AM org.apache.catalina.loader.WebappClassLoader
clearThreadLocalMap
SEVERE: The web application [/confluence] created a ThreadLocal with key of
type [com.atlassian.core.logging.ThreadLocalErrorCollection$2] (value
[com.atlassian.core.logging.ThreadLocalErrorCollection$2@1042d00]) and a
value of type [java.lang.Boolean] (value [false]) but failed to remove it
when the web application was stopped. This is very likely to create a
memory leak.
May 3, 2012 9:53:10 AM org.apache.catalina.loader.WebappClassLoader
clearThreadLocalMap
SEVERE: The web application [/confluence] created a ThreadLocal with key of
type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@12660a6]) and a
value of type [org.dom4j.DocumentFactory] (value
[org.dom4j.DocumentFactory@9352ad]) but failed to remove it when the web
application was stopped. This is very likely to create a memory leak.
May 3, 2012 9:53:10 AM org.apache.catalina.loader.WebappClassLoader
clearThreadLocalMap
SEVERE: The web application [/confluence] created a ThreadLocal with key of
type [com.atlassian.confluence.concurrent.ThreadLocalMap] (value
[com.atlassian.confluence.concurrent.ThreadLocalMap@191598]) and a value of
type [java.util.HashMap] (value [{}]) but failed to remove it when the web
application was stopped. This is very likely to create a memory leak.
log4j:ERROR LogMananger.repositorySelector was null likely due to error in
class reloading, using NOPLoggerRepository.
May 3, 2012 9:53:12 AM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8090
May 3, 2012 9:54:13 AM org.apache.tomcat.util.digester.SetPropertiesRule
begin
WARNING: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did
not find a matching property.
May 3, 2012 9:54:13 AM org.apache.tomcat.util.digester.SetPropertiesRule
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine} Setting property
'debug' to '0' did not find a matching property.
May 3, 2012 9:54:13 AM org.apache.tomcat.util.digester.SetPropertiesRule
begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property
'debug' to '0' did not find a matching property.
May 3, 2012 9:54:13 AM org.apache.tomcat.util.digester.SetPropertiesRule
begin
Re: Adding the manager app to a Standalone tomcat install
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Todd,
On 5/3/12 12:13 PM, Todd Seidenberg wrote:
However, when I click on the tomcat manager link, I get: HTTP
Status 404 - /manager/html
:(
Here's what I've done.
- I've determined the version of Tomcat that my standalone install
is using (6.0.32.)
- I've grabbed a tar.gz of the 6.0.32 standard tomcat and untarred
it.
- I've rsync'd the apache-tomcat-6.0.32/webapps/manager directory
to my standalone installation's webapp directory.
- I noted that I had NOTHING in my server.xml for the manager app.
(I do have context clauses in the server.xml for the main app that
the standalone tomcat was bundled with.)
- I made sure that tomcat was killed.
- I then started it up and tailed the log file (Note that the app
I'm running is called 'confluence.' It is running as expected.
Thanks for giving us that. Most people don't.
SEVERE: The web application [/confluence] created a ThreadLocal
with key of type
[com.opensymphony.xwork.ActionContext.ActionContextThreadLocal]
(value
[com.opensymphony.xwork.ActionContext$ActionContextThreadLocal@132ba74])
and a value of type [com.opensymphony.xwork.ActionContext] (value
[com.opensymphony.xwork.ActionContext@16f488d]) but failed to
remove it when the web application was stopped. This is very likely
to create a memory leak.
You might want to tell Confluence about these: they can really kill
your serer if you do a lot of hot-redeployments.
WARNING: [SetPropertiesRule]{Server} Setting property 'debug' to
'0' did not find a matching property. WARNING:
[SetPropertiesRule]{Server/Service/Engine} Setting property 'debug'
to '0' did not find a matching property. WARNING:
[SetPropertiesRule]{Server/Service/Engine/Host} Setting property
'debug' to '0' did not find a matching property. WARNING:
[SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting
property 'debug' to '0' did not find a matching property.
I'm seeing a pattern, here. You should remove the debug attributes
from those elements as they have not been a part of Tomcat since .. I
dunno 4.x?
INFO: Deploying configuration descriptor manager.xml
Good.
As you can see, the manager descriptor is deployed - and sure
enough the standard manager.xml file is created in
/usr/local/confluence-4/conf/Standalone/localhost.
Good.
However, I still don't get the manager app.
Bad. You mean you get a 404 Not Found?
It doesn't look like you are using anything in front of Tomcat like
httpd, are you? Do you have more than one Host in your server.xml?
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+ishwACgkQ9CaO5/Lv0PAfDwCeNxhvYfRaa/INxLjxSnwrPd7v
PsIAn00I3c3k2At9KdebWMWQAWnhJnsM
=PFCq
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
snip INFO: Deploying configuration descriptor manager.xml Good. As you can see, the manager descriptor is deployed - and sure enough the standard manager.xml file is created in /usr/local/confluence-4/conf/Standalone/localhost. Good. However, I still don't get the manager app. Bad. You mean you get a 404 Not Found? Thats correct. I get the: HTTP Status 404 - /manager/html message. Very strange. It doesn't look like you are using anything in front of Tomcat like httpd, are you? Do you have more than one Host in your server.xml? There is only one Host in my server.xml. We are currently running the AJP connector in the server.xml, and have httpd utilizing that connector to talk directly to the tomcat, but this is only for the convenience of redirecting a meaningful http address into the actual tomcat URL. We do not rely on it. Weird, huh? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+ishwACgkQ9CaO5/Lv0PAfDwCeNxhvYfRaa/INxLjxSnwrPd7v PsIAn00I3c3k2At9KdebWMWQAWnhJnsM =PFCq -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Adding the manager app to a Standalone tomcat install
From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Re: Adding the manager app to a Standalone tomcat install As you can see, the manager descriptor is deployed - and sure enough the standard manager.xml file is created in /usr/local/confluence-4/conf/Standalone/localhost. What exactly is in that manager.xml file? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
Todd Seidenberg wrote: snip INFO: Deploying configuration descriptor manager.xml Good. As you can see, the manager descriptor is deployed - and sure enough the standard manager.xml file is created in /usr/local/confluence-4/conf/Standalone/localhost. Good. However, I still don't get the manager app. Bad. You mean you get a 404 Not Found? Thats correct. I get the: HTTP Status 404 - /manager/html message. and is this an Apache or a Tomcat error page ? (easy to distinguish by the style) Very strange. It doesn't look like you are using anything in front of Tomcat like httpd, are you? Do you have more than one Host in your server.xml? There is only one Host in my server.xml. We are currently running the AJP connector in the server.xml, and have httpd utilizing that connector to talk directly to the tomcat, but this is only for the convenience of redirecting a meaningful http address into the actual tomcat URL. We do not rely on it. And this is what I suspect : the instructions used at the Apache level to proxy some URLs to Tomcat, do not cover the URL /manager/html. Therefore, Apache/mod_jk is not forwarding this to Tomcat, and instead it is Apache httpd itself which tries to find the resource corresponding to /manager/html; but it does not find it, so it returns a 404. Weird, huh? If my above suspicion is justified, then I would say that it's not weird at all. It is entirely predictable and actually very frequent as an error. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 André, On 5/3/12 1:44 PM, André Warnier wrote: And this is what I suspect : the instructions used at the Apache level to proxy some URLs to Tomcat, do not cover the URL /manager/html. Therefore, Apache/mod_jk is not forwarding this to Tomcat, and instead it is Apache httpd itself which tries to find the resource corresponding to /manager/html; but it does not find it, so it returns a 404. That would have been my first guess, but a) Todd didn't mention httpd until recently and b) his original 404 error page appeared to have the Tomcat 6.0.x footer (see Todd's 3rd message in the thread). - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+ixdUACgkQ9CaO5/Lv0PCUDACgmrcehNuzgNvh/M3cVyhzEP9v to8AoMNVo7B81WvlpQPcX7yVqrtNQCG3 =40nz -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
On Thu, May 3, 2012 at 11:44 AM, André Warnier a...@ice-sa.com wrote: Todd Seidenberg wrote: snip INFO: Deploying configuration descriptor manager.xml Good. As you can see, the manager descriptor is deployed - and sure enough the standard manager.xml file is created in /usr/local/confluence-4/conf/**Standalone/localhost. Good. However, I still don't get the manager app. Bad. You mean you get a 404 Not Found? Thats correct. I get the: HTTP Status 404 - /manager/html message. and is this an Apache or a Tomcat error page ? (easy to distinguish by the style) Very strange. It doesn't look like you are using anything in front of Tomcat like httpd, are you? Do you have more than one Host in your server.xml? There is only one Host in my server.xml. We are currently running the AJP connector in the server.xml, and have httpd utilizing that connector to talk directly to the tomcat, but this is only for the convenience of redirecting a meaningful http address into the actual tomcat URL. We do not rely on it. And this is what I suspect : the instructions used at the Apache level to proxy some URLs to Tomcat, do not cover the URL /manager/html. Therefore, Apache/mod_jk is not forwarding this to Tomcat, and instead it is Apache httpd itself which tries to find the resource corresponding to /manager/html; but it does not find it, so it returns a 404. Weird, huh? If my above suspicion is justified, then I would say that it's not weird at all. It is entirely predictable and actually very frequent as an error. I am definitely getting the 404 error from tomcat, not from httpd. Just to be safe, I have turned httpd completely off. I still get the same error. Here are the contents of my /usr/local/confluence-4/conf/Standalone/localhost/manager.xml file: (remember that this was generated when I first started tomcat.) ?xml version=1.0 encoding=UTF-8? !-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -- Context antiResourceLocking=false privileged=true useHttpOnly=true / --**--**- To unsubscribe, e-mail: users-unsubscribe@tomcat.**apache.orgusers-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Adding the manager app to a Standalone tomcat install
From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Re: Adding the manager app to a Standalone tomcat install Here are the contents of my /usr/local/confluence-4/conf/Standalone/localhost/manager.xml file: That looks reasonable. How about posting your server.xml file, preferably with comments stripped out and secure information obfuscated. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
On Thu, May 3, 2012 at 12:00 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Re: Adding the manager app to a Standalone tomcat install Here are the contents of my /usr/local/confluence-4/conf/Standalone/localhost/manager.xml file: That looks reasonable. How about posting your server.xml file, preferably with comments stripped out and secure information obfuscated. - Chuck Here's my server.xml stripped out of all secure info, as requested: Server port=8000 shutdown=SHUTDOWN debug=0 Service name=Tomcat-Standalone Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8090 minProcessors=5 maxProcessors=75 enableLookups=false redirectPort=8443 acceptCount=10 debug=0 connectionTimeout=2 useURIValidationHack=false URIEncoding=UTF-8 / Connector port=8009 protocol=AJP/1.3 redirectPort=8443 / Engine name=Standalone defaultHost=localhost debug=0 Host name=localhost debug=0 appBase=webapps unpackWARs=true autoDeploy=true Context path=/confluence docBase=../confluence debug=0 reloadable=false useHttpOnly=true Manager pathname= / Resource -PRIVATE STUFF REMOVED- / Resource -PRIVATE STUFF REMOVED- / Resource -PRIVATE STUFF REMOVED- / Resource -PRIVATE STUFF REMOVED- / Resource -PRIVATE STUFF REMOVED- / Resource -PRIVATE STUFF REMOVED- / /Context /Host /Engine /Service /Server THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
Todd Seidenberg wrote: ... Here's my server.xml stripped out of all secure info, as requested: Server port=8000 shutdown=SHUTDOWN debug=0 Service name=Tomcat-Standalone Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8090 minProcessors=5 is that really Tomcat 4.x that you are using ? How about platform, OS, JVM, Tomcat versions etc.. ? - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
On Thu, May 3, 2012 at 12:39 PM, André Warnier a...@ice-sa.com wrote: Todd Seidenberg wrote: ... Here's my server.xml stripped out of all secure info, as requested: Server port=8000 shutdown=SHUTDOWN debug=0 Service name=Tomcat-Standalone Connector className=org.apache.coyote.**tomcat4.CoyoteConnector port=8090 minProcessors=5 is that really Tomcat 4.x that you are using ? How about platform, OS, JVM, Tomcat versions etc.. ? Its actually not tomcat 4.0 Its 6.0.32. I think this server.xml, that came with the standalone app (confluence) has some legacy still hanging around from the 4.0 days. Here's the version.sh output: # /usr/local/confluence-4/bin/version.sh Server startup logs are located in /usr/local/confluence-4/logs/catalina.out Using CATALINA_BASE: /usr/local/confluence-4 Using CATALINA_HOME: /usr/local/confluence-4 Using CATALINA_TMPDIR: /usr/local/confluence-4/temp Using JRE_HOME:/usr/local/confluence-4/jre/ Using CLASSPATH: /usr/local/confluence-4/bin/bootstrap.jar Using CATALINA_PID:/usr/local/confluence-4/work/catalina.pid Server version: Apache Tomcat/6.0.32 Server built: February 2 2011 2003 Server number: 6.0.32.0 OS Name:Linux OS Version: 2.6.16.54-0.2.8-default Architecture: i386 JVM Version:1.6.0_26-b03 JVM Vendor: Sun Microsystems Inc. --**--**- To unsubscribe, e-mail: users-unsubscribe@tomcat.**apache.orgusers-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Todd, On 5/3/12 2:56 PM, Todd Seidenberg wrote: On Thu, May 3, 2012 at 12:39 PM, André Warnier a...@ice-sa.com wrote: Here's my server.xml stripped out of all secure info, as requested: Server port=8000 shutdown=SHUTDOWN debug=0 Service name=Tomcat-Standalone Connector className=org.apache.coyote.**tomcat4.CoyoteConnector port=8090 minProcessors=5 is that really Tomcat 4.x that you are using ? How about platform, OS, JVM, Tomcat versions etc.. ? Its actually not tomcat 4.0 Its 6.0.32. I think this server.xml, that came with the standalone app (confluence) has some legacy still hanging around from the 4.0 days. I'm not sure how this server.xlm could even start up properly with that class name in there. Are you sure this is the one being used? Try to completely break the XML or remove your confluence Context and see if it starts up. Maybe you've been banging your head against the wrong server.xml for some reason. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+i4iMACgkQ9CaO5/Lv0PAKVwCgsebTWiCL7zSlEtpj6eg9uyoq g4gAnj4XtkJ8moamUNStjD7E9XwpDa3M =4HcG -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Adding the manager app to a Standalone tomcat install
From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Re: Adding the manager app to a Standalone tomcat install Server port=8000 shutdown=SHUTDOWN debug=0 Service name=Tomcat-Standalone Connector className=org.apache.coyote.**tomcat4.CoyoteConnector port=8090 minProcessors=5 is that really Tomcat 4.x that you are using ? How about platform, OS, JVM, Tomcat versions etc.. ? Its actually not tomcat 4.0 Its 6.0.32. Luckily, there is no longer a className attribute for Connector, so it was ignored. However, this does indicate a rather cavalier and sloppy attitude for confluence, so perhaps you should try to get them to clean up their act. I would have a hard time trusting much of anything at this point. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
On Thu, May 3, 2012 at 1:58 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Re: Adding the manager app to a Standalone tomcat install Server port=8000 shutdown=SHUTDOWN debug=0 Service name=Tomcat-Standalone Connector className=org.apache.coyote.**tomcat4.CoyoteConnector port=8090 minProcessors=5 is that really Tomcat 4.x that you are using ? How about platform, OS, JVM, Tomcat versions etc.. ? Its actually not tomcat 4.0 Its 6.0.32. Luckily, there is no longer a className attribute for Connector, so it was ignored. However, this does indicate a rather cavalier and sloppy attitude for confluence, so perhaps you should try to get them to clean up their act. I would have a hard time trusting much of anything at this point. - Chuck I agree. However, I can deploy other apps. The base examples that come with tomcat work, for example. I have removed all of the offending stuff from the server.xml but the manager/html still gives me a 404. Just for giggles, I have removed the confluence Context from the server.xml file as well, and restarted. I still get the ROOT page, but the manager still gives me a 404. Any other thoughts? - Thanks, Todd THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Adding the manager app to a Standalone tomcat install
From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Re: Adding the manager app to a Standalone tomcat install I have removed all of the offending stuff from the server.xml but the manager/html still gives me a 404. Just to be sure, exactly what URL are you using to try to access the manager? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
On Thu, May 3, 2012 at 3:03 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Re: Adding the manager app to a Standalone tomcat install I have removed all of the offending stuff from the server.xml but the manager/html still gives me a 404. Just to be sure, exactly what URL are you using to try to access the manager? - Chuck http://hostname:8090/manager/html THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Adding the manager app to a Standalone tomcat install
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Todd, On 5/3/12 5:22 PM, Todd Seidenberg wrote: On Thu, May 3, 2012 at 3:03 PM, Caldarale, Charles R chuck.caldar...@unisys.com wrote: From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Re: Adding the manager app to a Standalone tomcat install I have removed all of the offending stuff from the server.xml but the manager/html still gives me a 404. Just to be sure, exactly what URL are you using to try to access the manager? - Chuck http://hostname:8090/manager/html Grasping at straws: is there an old instance of Tomcat still running and bound to your port? If you enable the AccessLogValve, can you confirm that the request is actually being handled by the instance you are launching? This is truly strange. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+jGN8ACgkQ9CaO5/Lv0PDy9wCdGiyBxh4YA+K4chnAQvp0nhpT N8UAn3gcQebCujSwO5YEVADUoWkrKGel =qT3S -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Adding the manager app to a Standalone tomcat install
Folks, I'm trying to use the manager app, so that I can collect performance metrics on our running Standalone Tomcat setup. The standalone came bundled with an application - in an effort to provide a completely encapsulated solution that runs right out of the box. The problem is I'd like to collect performance data, and know that running the manager app will provide this information for me. Is it possible to install the manager app in an install like this? - Thanks, Todd
RE: Adding the manager app to a Standalone tomcat install
From: Todd Seidenberg [mailto:todd.seidenb...@gmail.com] Subject: Adding the manager app to a Standalone tomcat install I'm trying to use the manager app, so that I can collect performance metrics on our running Standalone Tomcat setup. What kind of performance information do you think the manager webapp will give you? Have you looked at just enabling the AccessLogValve? For real performance data, you might want to look at these: http://moskito.anotheria.net/ http://code.google.com/p/psi-probe/ Is it possible to install the manager app in an install like this? Sure - get a normal Tomcat download for the same version, and copy the manager webapp and its associated manager.xml file over to your installation. You'll likely need to update conf/tomcat-users.xml or whatever authentication mechanism you have employed in order to access the manager. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
