tomcat manager application access
Hi, We have a requirement to allow the manager application of tomcat to be accessed only from the local machine, it should not be accessed from remote. What are the possible ways to achive this. Can we specify filter request in the manager application context as below context value=/manager Valve className=org.apache.catalina.valves.RemoteHostValve allow=127.0.0.1/ cotext Will it only allow requests from 127.0.0.1 or should we specify deny attribute also. - Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less.
Re: manager application
Hi, after installing tomcat there is no user configured to access these apps. To do this, add the following to your tomcat-users.xml: role rolename=manager/ role rolename=admin/ user username=user password=pw roles=admin,manager/ btw: when using tomcat 5.5.x you have to download the admin app separately, since it is no longer delivered with tomcat. Jens Joachim Syscon GmbH E-Mail: [EMAIL PROTECTED] - Original Message - From: P.M [EMAIL PROTECTED] To: Jarkarta - TOMCAT Apache tomcat-user@jakarta.apache.org Sent: Sunday, February 13, 2005 3:42 PM Subject: manager application Hi, I open the localhost:8080 without any trouble now, but i hace an error message 403 everyting that i try to access to manager or admin applications. i tested all username and password which are in tomcat-users.xml, but nothing work.. i know from windows install exe file, that another profile existed : admin with empty password...but even if this one doesn't work. does anyone have seen it already ? thx, Maileen __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: manager application
To use the manager app you have to add a user into the tomcat-users.xml with the manager role. Ta Matt -Original Message- From: P.M [mailto:[EMAIL PROTECTED] Sent: 13 February 2005 14:43 To: Jarkarta - TOMCAT Apache Subject: manager application Hi, I open the localhost:8080 without any trouble now, but i hace an error message 403 everyting that i try to access to manager or admin applications. i tested all username and password which are in tomcat-users.xml, but nothing work.. i know from windows install exe file, that another profile existed : admin with empty password...but even if this one doesn't work. does anyone have seen it already ? thx, Maileen __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
manager application
Hi, I open the localhost:8080 without any trouble now, but i hace an error message 403 everyting that i try to access to manager or admin applications. i tested all username and password which are in tomcat-users.xml, but nothing work.. i know from windows install exe file, that another profile existed : admin with empty password...but even if this one doesn't work. does anyone have seen it already ? thx, Maileen __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with Manager application
Hello All, I've recently gotten a new machine and installed linux Fedora Core 1 j2sdk1.4.2_03 jakarta-tomcat-5.0.19 netbeans3.6 I've played around with netbeans and tomcat in the past and have some web apps that I've created and that run fine on an older machine. On the new machine, when I try to use the manager application that comes with tomcat to deploy one of my app, I get this exception. type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: Servlet execution threw an exception root cause java.lang.NoClassDefFoundError: javax/servlet/ServletInputStream org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServlet.java:142) javax.servlet.http.HttpServlet.service(HttpServlet.java:709) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) note The full stack trace of the root cause is available in the Apache Tomcat/5.0.29 logs. I used netbeans to create the simplest app I could and still got the same error. I looked thru the archives on this mailing list and the closest thing I found was something that said that java.lang.NoClassDefFoundError is often caused by having multiple instances of a jar file on the machine. I searched around and found that javax/servlet/ServletInputStream is in tomcat_install_dir/commons/lib/servlet-api.jar, so I searched my machine for it and found two instances. One where it should be for tomcat and another in my home directory where netbeans is installed. This looks ok to me but just on a whim I deleted the netbaens install dir and nothing changed. So now I'm kinda stuck. On my older installation of tomcat everything works great, anybody have a good idea how to track down my problem?? Oh yea, when I start tomcat it echos [EMAIL PROTECTED] root]# /usr/local/jakarta-tomcat-5.0.19/bin/startup.sh Using CATALINA_BASE: /usr/local/jakarta-tomcat-5.0.19 Using CATALINA_HOME: /usr/local/jakarta-tomcat-5.0.19 Using CATALINA_TMPDIR: /usr/local/jakarta-tomcat-5.0.19/temp Using JAVA_HOME: /usr/local/j2sdk1.4.2_03 which looks correct to me Ideas??? Oh yea, Oh yea it I just place the war file for my app in the tomcat webapps directory and stop and restart tomcat it deploys and runs fine TIA Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem with Manager application
Hi, There's probably an older servlet.jar (not servlet-api.jar, which is the name for Servlet Spec 2.4) around somewhere on the NetBeans runtime classpath. Or possibly a bigger j2ee.jar containing servlet and other J2EE APIs. So you're on the right debugging path: multiple instances of the servlet API jar (but with different names) are the most likely cause for this error. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Dave Robbins [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 23, 2004 1:58 PM To: [EMAIL PROTECTED] Subject: Problem with Manager application Hello All, I've recently gotten a new machine and installed linux Fedora Core 1 j2sdk1.4.2_03 jakarta-tomcat-5.0.19 netbeans3.6 I've played around with netbeans and tomcat in the past and have some web apps that I've created and that run fine on an older machine. On the new machine, when I try to use the manager application that comes with tomcat to deploy one of my app, I get this exception. type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: Servlet execution threw an exception root cause java.lang.NoClassDefFoundError: javax/servlet/ServletInputStream org.apache.catalina.manager.HTMLManagerServlet.doPost(HTMLManagerServ let.java:142) javax.servlet.http.HttpServlet.service(HttpServlet.java:709) javax.servlet.http.HttpServlet.service(HttpServlet.java:802) note The full stack trace of the root cause is available in the Apache Tomcat/5.0.29 logs. I used netbeans to create the simplest app I could and still got the same error. I looked thru the archives on this mailing list and the closest thing I found was something that said that java.lang.NoClassDefFoundError is often caused by having multiple instances of a jar file on the machine. I searched around and found that javax/servlet/ServletInputStream is in tomcat_install_dir/commons/lib/servlet-api.jar, so I searched my machine for it and found two instances. One where it should be for tomcat and another in my home directory where netbeans is installed. This looks ok to me but just on a whim I deleted the netbaens install dir and nothing changed. So now I'm kinda stuck. On my older installation of tomcat everything works great, anybody have a good idea how to track down my problem?? Oh yea, when I start tomcat it echos [EMAIL PROTECTED] root]# /usr/local/jakarta-tomcat-5.0.19/bin/startup.sh Using CATALINA_BASE: /usr/local/jakarta-tomcat-5.0.19 Using CATALINA_HOME: /usr/local/jakarta-tomcat-5.0.19 Using CATALINA_TMPDIR: /usr/local/jakarta-tomcat-5.0.19/temp Using JAVA_HOME: /usr/local/j2sdk1.4.2_03 which looks correct to me Ideas??? Oh yea, Oh yea it I just place the war file for my app in the tomcat webapps directory and stop and restart tomcat it deploys and runs fine TIA Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Manager application in TC 4.1
Hi, Note the /manager is still valid, it's just not the HTML version. That's at /manager/html. The two are both the manager webapp and both valid. So you might not need to change anything. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Andoni [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 12, 2004 4:59 PM To: Tomcat Users List Subject: Manager application in TC 4.1 Hello, I have just upgraded to Tomcat 4.1 and I have encountered the fact that the manager application is now at: www.mydomain.com:8080/manager/html/ What is the simples way to change this to be at www.mydomain.com:8080/manager ? I have changed the mappings but that breaks the mappings in the manager app. I know the comment in the manager's web.xml file says just to change the class but is that right? I think that's just a legacy comment. Thanks, Andoni This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Manager application in TC 4.1
Hello, I have just upgraded to Tomcat 4.1 and I have encountered the fact that the manager application is now at: www.mydomain.com:8080/manager/html/ What is the simples way to change this to be at www.mydomain.com:8080/manager ? I have changed the mappings but that breaks the mappings in the manager app. I know the comment in the manager's web.xml file says just to change the class but is that right? I think that's just a legacy comment. Thanks, Andoni
RE: Manager application in TC 4.1
put an index.html page under $CATALINA_HOME/server/webapps/manager and have it contain a link to /html or a meta refresh. -Original Message- From: Andoni [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 12, 2004 3:59 PM To: Tomcat Users List Subject: Manager application in TC 4.1 Hello, I have just upgraded to Tomcat 4.1 and I have encountered the fact that the manager application is now at: www.mydomain.com:8080/manager/html/ What is the simples way to change this to be at www.mydomain.com:8080/manager ? I have changed the mappings but that breaks the mappings in the manager app. I know the comment in the manager's web.xml file says just to change the class but is that right? I think that's just a legacy comment. Thanks, Andoni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Manager application in TC 4.1
Ok, now I have rebooted the server I know it doesn't work! I did exactly what it said to do in the comment and this did not work. The same thing (replacing the class name) *did* work in 4.0.4, which was my last version, which is why I tried it in the 1st place :-) Anyway any suggestion as to whether it is possible to change the URL for the manager application in Tomcat 4.1.24 are welcome. Thanks in advance. Andoni. - Original Message - From: Andoni [EMAIL PROTECTED] Newsgroups: gmane.comp.jakarta.tomcat.user Sent: Tuesday, October 12, 2004 9:58 PM Subject: Manager application in TC 4.1 Hello, I have just upgraded to Tomcat 4.1 and I have encountered the fact that the manager application is now at: www.mydomain.com:8080/manager/html/ What is the simples way to change this to be at www.mydomain.com:8080/manager ? I have changed the mappings but that breaks the mappings in the manager app. I know the comment in the manager's web.xml file says just to change the class but is that right? I think that's just a legacy comment. Thanks, Andoni - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat manager application problems
Hi, We use the Manager webapp all the time (via its HTML interface, although some people prefer the Ant tasks), without significant issues. Of course, the usual advice of trying the latest stable version (5.0.28 at this time) applies: specifically in this case, there have been numerous bug fixes relevant to the stability and operation of the Manager webapp between 5.0.18 and 5.0.28. The approach of running applications on separate Tomcat instances also should never be discounted. It has a high operational value, although of course at an increased maintenance cost. We do this for mission-critical applications. Yoav Shapira Millennium Research Informatics -Original Message- From: Noah Davis [mailto:[EMAIL PROTECTED] Sent: Monday, September 13, 2004 4:53 PM To: [EMAIL PROTECTED] Subject: tomcat manager application problems I recently deployed the manager app for Tomcat/5.0.18 with the hope that I could use it to deploy apps without taking down all the other applications running on the server. However, I've had nothing but problems with the tomcat manager. I've been using mostly the HTML version. Some problems have included: 1. A redeployed application complains that it cannot find JSP files for compilation. 2. During war file upload, a whitescreen appears without any error messages. I'd like to give more detailed error messages, but since the problems seem to differ each time, I thought I'd inquire as to what others' experiences have been. Is the manager app reliable? Should I be investigating running separate instances of tomcat for all my applications, or is there some configuration settings I need to be checking? Thanks, Noah - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
question about non-responding commands in tomcat 5.5.1 manager application
Hello, Tomcat Gurus, I have installed tomcat 5.5.1 under linux redhat 9, with j2sdk-1.4.2_05 and the compat package to make it compatable. Everything works fine until I came to the point of using tomcat manager. THe command button (start, stop..) didn't respond at all. I checked logs/catalina.out and there is nothing there. I can only start an appliation by putting my web application under webapps and stop and restart tomcat, the application works OK though. Could someone please help me with the tomcat manager issue? It is so weird. THanks ginger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: question about non-responding commands in tomcat 5.5.1 manager application
Hi, I think I inadvertently broke the HTML manager (Ant should still work fine) in 5.5.1 when I added the JavaScript confirmation prompts to the start/stop/deploy/undeploy commands. I added these prompts to address existing Bugzilla requests, but the single quotes are being removed somewhere along the rendering pipeline, resulting in Bugzilla 29485 being reopened. Watch that issue if you're interested, I'll make sure it's fixed for 5.5.3 (it's too late for 5.5.2 as I finished building that around 12:30pm today). Yoav Shapira Millennium Research Informatics -Original Message- From: Ginger Cheng [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 14, 2004 3:23 PM To: [EMAIL PROTECTED] Subject: question about non-responding commands in tomcat 5.5.1 manager application Hello, Tomcat Gurus, I have installed tomcat 5.5.1 under linux redhat 9, with j2sdk-1.4.2_05 and the compat package to make it compatable. Everything works fine until I came to the point of using tomcat manager. THe command button (start, stop..) didn't respond at all. I checked logs/catalina.out and there is nothing there. I can only start an appliation by putting my web application under webapps and stop and restart tomcat, the application works OK though. Could someone please help me with the tomcat manager issue? It is so weird. THanks ginger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat manager application problems
Thanks for your response. I upgraded tomcat to 5.0.28 and got the manager app working using Ant, which is what I really wanted anyhow. I still had some issues using the HTML version. I uploaded a WAR file successfully, but when I ran the application, I got a 404 error, and this error appeared in the log file: - Root Cause - java.lang.NoClassDefFoundError: org/apache/commons/beanutils/Converter at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:1610) at java.lang.Class.getConstructor0(Class.java:1922) at java.lang.Class.newInstance0(Class.java:278) at java.lang.Class.newInstance(Class.java:261) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:98 7) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:862) I'm happy enough with the ant version, but don't understand quite entirely why it behaves differently if I use the HTML client. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 14, 2004 8:59 AM To: Tomcat Users List Subject: RE: tomcat manager application problems Hi, We use the Manager webapp all the time (via its HTML interface, although some people prefer the Ant tasks), without significant issues. Of course, the usual advice of trying the latest stable version (5.0.28 at this time) applies: specifically in this case, there have been numerous bug fixes relevant to the stability and operation of the Manager webapp between 5.0.18 and 5.0.28. The approach of running applications on separate Tomcat instances also should never be discounted. It has a high operational value, although of course at an increased maintenance cost. We do this for mission-critical applications. Yoav Shapira Millennium Research Informatics -Original Message- From: Noah Davis [mailto:[EMAIL PROTECTED] Sent: Monday, September 13, 2004 4:53 PM To: [EMAIL PROTECTED] Subject: tomcat manager application problems I recently deployed the manager app for Tomcat/5.0.18 with the hope that I could use it to deploy apps without taking down all the other applications running on the server. However, I've had nothing but problems with the tomcat manager. I've been using mostly the HTML version. Some problems have included: 1. A redeployed application complains that it cannot find JSP files for compilation. 2. During war file upload, a whitescreen appears without any error messages. I'd like to give more detailed error messages, but since the problems seem to differ each time, I thought I'd inquire as to what others' experiences have been. Is the manager app reliable? Should I be investigating running separate instances of tomcat for all my applications, or is there some configuration settings I need to be checking? Thanks, Noah - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat manager application problems
I recently deployed the manager app for Tomcat/5.0.18 with the hope that I could use it to deploy apps without taking down all the other applications running on the server. However, I've had nothing but problems with the tomcat manager. I've been using mostly the HTML version. Some problems have included: 1. A redeployed application complains that it cannot find JSP files for compilation. 2. During war file upload, a whitescreen appears without any error messages. I'd like to give more detailed error messages, but since the problems seem to differ each time, I thought I'd inquire as to what others' experiences have been. Is the manager app reliable? Should I be investigating running separate instances of tomcat for all my applications, or is there some configuration settings I need to be checking? Thanks, Noah - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deploying problem with ant and the manager application
Hi
I'm trying to deploy a application using ANT but I don't get it to work.
I know that I'm doing som general error here, but since it's my first
build.xml script I just couldn't figure it out.
My install task looks something like this:
target name=list
description=List installed applications on servelet
container.
listurl=${manager.url}
username=${manager.username}
password=${manager.password}
/
/target
And I get the following error:
BUILD FAILED
file:/home/johan/development/javaxptest/build.xml:183:
java.io.FileNotFoundException:
jar:file:/home/johan/development/javaxptest/dist/xptest.war (No such
file or directory)
But my script have created a xptest.war file in the directory so I
don't know whats wrong.
Is it a permission error or what have I missed?
Please help
Regards, Johan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
AW: Manager Application does not remove webapp correctly
Hi Doug, if I put struts.jar and securityfilter.jar in the tomcat common/lib folder it works. However, I am not allowed to put these jars there. I have to ship them with the webapp, so I am still facing this problem that Tomcat Manager is not removing the app correctly. Any further idea? thx, Dirk -Ursprüngliche Nachricht- Von: Parsons Technical Services [mailto:[EMAIL PROTECTED] Gesendet: Montag, 29. März 2004 03:09 An: Tomcat Users List Betreff: Re: Manager Application does not remove webapp correctly Dirk, Have you tried putting these jars in common/lib? This way they are loaded on Tomcat start-up and will be available to your app without impacting the deploy/undeploy. Doug www.parsonstechnical.com - Original Message - From: Just Fun 4 You [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, March 28, 2004 7:06 PM Subject: Manager Application does not remove webapp correctly Hi, I am using Tomcat 4.1.29 and deploy/undeploy my webapp with the Tomcat Manager Application. My webapp uses Struts 1.1, SecurityFilter and Log4J. The first deploy works fine. Then, when I remove the webapp, the app folder is not totally removed from the tomcat webapps directory. The folder 'lib' with the files struts.jar and securityfilter.jar remain. It is not even possible to delete them manually as tomcat still holds a process on them. Have no idea what happens here!? Can somebody help? thx, Dirk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Manager Application does not remove webapp correctly
Dirk, Sorry, but at this point it has move above my current level on Tomcat. Hopefully someone more knowledgeable will chime in. Doug - Original Message - From: Just Fun 4 You [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Monday, March 29, 2004 3:51 AM Subject: AW: Manager Application does not remove webapp correctly Hi Doug, if I put struts.jar and securityfilter.jar in the tomcat common/lib folder it works. However, I am not allowed to put these jars there. I have to ship them with the webapp, so I am still facing this problem that Tomcat Manager is not removing the app correctly. Any further idea? thx, Dirk -Ursprüngliche Nachricht- Von: Parsons Technical Services [mailto:[EMAIL PROTECTED] Gesendet: Montag, 29. März 2004 03:09 An: Tomcat Users List Betreff: Re: Manager Application does not remove webapp correctly Dirk, Have you tried putting these jars in common/lib? This way they are loaded on Tomcat start-up and will be available to your app without impacting the deploy/undeploy. Doug www.parsonstechnical.com - Original Message - From: Just Fun 4 You [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, March 28, 2004 7:06 PM Subject: Manager Application does not remove webapp correctly Hi, I am using Tomcat 4.1.29 and deploy/undeploy my webapp with the Tomcat Manager Application. My webapp uses Struts 1.1, SecurityFilter and Log4J. The first deploy works fine. Then, when I remove the webapp, the app folder is not totally removed from the tomcat webapps directory. The folder 'lib' with the files struts.jar and securityfilter.jar remain. It is not even possible to delete them manually as tomcat still holds a process on them. Have no idea what happens here!? Can somebody help? thx, Dirk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Manager Application does not remove webapp correctly
Does anybody else can jump in here? I got stuck. Obviously there is a big problem with Tomcat 4 and Struts. Tomcat does not release the struts.jar, commons-validator.jar and securityfilter.jar. All these packages have some property files. I assume this could be the problem, why Tomcat still holds processes on these jars because there might be a problem for tomcat with i/o operations. But I am just guessing. Is there no struts user who deploys/undeploys with the Tomcat Manager Application and experiences the same problem??! Dirk -Ursprüngliche Nachricht- Von: Parsons Technical Services [mailto:[EMAIL PROTECTED] Gesendet: Montag, 29. März 2004 14:43 An: Tomcat Users List Betreff: Re: Manager Application does not remove webapp correctly Dirk, Sorry, but at this point it has move above my current level on Tomcat. Hopefully someone more knowledgeable will chime in. Doug - Original Message - From: Just Fun 4 You [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Monday, March 29, 2004 3:51 AM Subject: AW: Manager Application does not remove webapp correctly Hi Doug, if I put struts.jar and securityfilter.jar in the tomcat common/lib folder it works. However, I am not allowed to put these jars there. I have to ship them with the webapp, so I am still facing this problem that Tomcat Manager is not removing the app correctly. Any further idea? thx, Dirk -Ursprüngliche Nachricht- Von: Parsons Technical Services [mailto:[EMAIL PROTECTED] Gesendet: Montag, 29. März 2004 03:09 An: Tomcat Users List Betreff: Re: Manager Application does not remove webapp correctly Dirk, Have you tried putting these jars in common/lib? This way they are loaded on Tomcat start-up and will be available to your app without impacting the deploy/undeploy. Doug www.parsonstechnical.com - Original Message - From: Just Fun 4 You [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, March 28, 2004 7:06 PM Subject: Manager Application does not remove webapp correctly Hi, I am using Tomcat 4.1.29 and deploy/undeploy my webapp with the Tomcat Manager Application. My webapp uses Struts 1.1, SecurityFilter and Log4J. The first deploy works fine. Then, when I remove the webapp, the app folder is not totally removed from the tomcat webapps directory. The folder 'lib' with the files struts.jar and securityfilter.jar remain. It is not even possible to delete them manually as tomcat still holds a process on them. Have no idea what happens here!? Can somebody help? thx, Dirk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Manager Application does not remove webapp correctly
Hi, I am using Tomcat 4.1.29 and deploy/undeploy my webapp with the Tomcat Manager Application. My webapp uses Struts 1.1, SecurityFilter and Log4J. The first deploy works fine. Then, when I remove the webapp, the app folder is not totally removed from the tomcat webapps directory. The folder 'lib' with the files struts.jar and securityfilter.jar remain. It is not even possible to delete them manually as tomcat still holds a process on them. Have no idea what happens here!? Can somebody help? thx, Dirk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Manager Application does not remove webapp correctly
Dirk, Have you tried putting these jars in common/lib? This way they are loaded on Tomcat start-up and will be available to your app without impacting the deploy/undeploy. Doug www.parsonstechnical.com - Original Message - From: Just Fun 4 You [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, March 28, 2004 7:06 PM Subject: Manager Application does not remove webapp correctly Hi, I am using Tomcat 4.1.29 and deploy/undeploy my webapp with the Tomcat Manager Application. My webapp uses Struts 1.1, SecurityFilter and Log4J. The first deploy works fine. Then, when I remove the webapp, the app folder is not totally removed from the tomcat webapps directory. The folder 'lib' with the files struts.jar and securityfilter.jar remain. It is not even possible to delete them manually as tomcat still holds a process on them. Have no idea what happens here!? Can somebody help? thx, Dirk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Manager application remove function doesn't remove deployed directory location
Hello all, My platform is Windows 2000 Apache-Tomcat 4.1.29, J2SDK1.4.2_01. I have written a struts-based web application. I install the application using the tomcat manager application and things are fine. When I try to remove the application using the tomcat manager application (for instance an application installed at context 'WebApp': http://localhost:8080/manager/remove?path=/WebApp The manager application responds with OK - Removed application at context path /WebApp The problem is that the deployed location still exists. The deployed directory has one file: WEB-INF/lib/struts.jar. The deployed directory cannot be removed, windows claims stuts.jar is still in use. If I restart Tomcat the deployed directory can be manually removed. Using the manager application to stop the application doesn't seem to help. I want my application to uninstall without writing a routine to manually directories, etc. It would be nice to have this happen thru Tomcat. Does anybody have any ideas about this? Thanks. David Harvey eXegesys, Inc. www.exegesys.com
how to start the root context with manager application
Hello, we recently installed Tomcat 4.1.24 on a SUSE 8.2 Linux machine and are trying to get to know how to start, stop and reload applications. So far, Tomcat and the applications seem to be running fine. We have defined our application to run as the default or ROOT application. In the Tomcat manager web application we can stop and reload this root application, but can not start it after having stopped it. The following error appears when trying to start the application at path / (http://xx/manager/html/start?path=/) FAIL - Application at context path / could not be started The documentation states The context path must start with a slash character, unless you are referencing the ROOT web application -- in which case the context path must be a zero-length string., so we tried replacing the / by (http://xx/manager/html/start?path=;) This results in a similar error: FAIL - No context exists for path How should we represent the zero-length string to start the ROOT application? The / is accepted in the stop (http://xx/manager/html/stop?path=/) and reload (http://xx/manager/html/reload?path=/)commands). We only tried this in the Manager web application. Kind regards, Francis Brouns - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
question on manager application
I am in need to deploy a WAR file to a remote Tomcat4 and need to have the WAR file expanded. Any pointers as to what the URL to the manager app would look like (i.e the 'war' parameter - btw, what's the difference between file:/.../foo.war and jar:file:/.../foo.war!/ ???) and to expand the archive? tia -t - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: question on manager application
I'm not sure I understand your question. I deploy WAR files regularly to a remote Tomcat4 and it's very easy: 1. Go to the Manager application in your remote Tomcat. 2. If there is already an old version of the servlet on your remote Tomcat, remove the old version of the servlet using the Remove command that is on the same line as the context name in the Applications table. 3. Use the Upload a WAR file to install section to install the new version of the WAR file. Use the Browse button to find the WAR file on *your* system, then click the Install button. It may take a few seconds for the Install to complete, depending on the size of the WAR file but when it is done, the Message area near the top of the Manager application will tell you that the installation was successful (unless your WAR file has problems in it; then you'll get an error message.) Tomcat takes care of all the expanding of the WAR file for you if you do it this way. Rhino - Original Message - From: T C K [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 11:53 AM Subject: question on manager application I am in need to deploy a WAR file to a remote Tomcat4 and need to have the WAR file expanded. Any pointers as to what the URL to the manager app would look like (i.e the 'war' parameter - btw, what's the difference between file:/.../foo.war and jar:file:/.../foo.war!/ ???) and to expand the archive? tia -t - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 4.0.4 Manager Application
When I try and run the following command: http://localhost:8080/manager/stop?path=/foo I get the following error: java.lang.NoSuchMethodError: org.apache.naming.resources.ProxyDirContext.getDirContext() Ljavax/naming/directory/DirContext; at org.apache.catalina.core.StandardContext.stop (StandardContext.java:3479) at org.apache.catalina.core.StandardHost.stop(StandardHost.java:889) at org.apache.catalina.servlets.HTMLManagerServlet.stop (HTMLManagerServlet.java:418) at org.apache.catalina.servlets.HTMLManagerServlet.doGet (HTMLManagerServlet.java:139) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (ApplicationFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter (ApplicationFilterChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:243) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke (ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:190) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:566) at org.apache.catalina.authenticator.AuthenticatorBase.invoke (AuthenticatorBase.java:531) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:564) at org.apache.catalina.valves.CertificatesValve.invoke (CertificatesValve.java:246) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke (ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke (StandardContext.java:2347) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:180) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:566) at org.apache.catalina.valves.ErrorDispatcherValve.invoke (ErrorDispatcherValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:564) at org.apache.catalina.valves.ErrorReportValve.invoke (ErrorReportValve.java:170) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:564) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke (ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:174) at org.apache.catalina.core.StandardPipeline.invokeNext (StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke (StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke (ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process (HttpProcessor.java:1027) at org.apache.catalina.connector.http.HttpProcessor.run (HttpProcessor.java:1125) at java.lang.Thread.run(Thread.java:536) Thanks for any help. I hope this message is appropriate for this list. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bit confused: Admin Tool vs Manager Application
AFAICT, you'll need to update if you want that functionality. -Tim [EMAIL PROTECTED] wrote: Hi. Is it a simple mater of downloading some java code from jakarta.apache.org and putting it in the proper folder ? Does it require an upgrade from 404 to get the full functionalities? TIA :-) Bill Barker wrote: Tomcat 4.0.4 only has the 'manager' (which is similar to the 4.1.x 'manager' (but with fewer features), and the 3.3.x 'admin'). [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] THX, but where does 404 fit in. It's neither 3.3+ or 4.1+ TIA - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bit confused: Admin Tool vs Manager Application
THX, but where does 404 fit in. It's neither 3.3+ or 4.1+ TIA Bill Barker wrote: The 'admin' Context in 3.3.x is similar tothe 'manager' Context in 4.1.x. There are big difference when you get down to the specifics (e.g. 3.3 doesn't include Ant tasks), but in Big Picture terms, they do much the same thing from the HTML interface. [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi All. I'm on TC404, looking at manager configuration. Is Administration Tool only available in TC3.x? Is the Manager Applicatio only available in TC4.1+? Seems like TC404 is somewhere in between. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bit confused: Admin Tool vs Manager Application
Tomcat 4.0.4 only has the 'manager' (which is similar to the 4.1.x 'manager' (but with fewer features), and the 3.3.x 'admin'). [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] THX, but where does 404 fit in. It's neither 3.3+ or 4.1+ TIA Bill Barker wrote: The 'admin' Context in 3.3.x is similar tothe 'manager' Context in 4.1.x. There are big difference when you get down to the specifics (e.g. 3.3 doesn't include Ant tasks), but in Big Picture terms, they do much the same thing from the HTML interface. [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi All. I'm on TC404, looking at manager configuration. Is Administration Tool only available in TC3.x? Is the Manager Applicatio only available in TC4.1+? Seems like TC404 is somewhere in between. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bit confused: Admin Tool vs Manager Application
Hi. Is it a simple mater of downloading some java code from jakarta.apache.org and putting it in the proper folder ? Does it require an upgrade from 404 to get the full functionalities? TIA :-) Bill Barker wrote: Tomcat 4.0.4 only has the 'manager' (which is similar to the 4.1.x 'manager' (but with fewer features), and the 3.3.x 'admin'). [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] THX, but where does 404 fit in. It's neither 3.3+ or 4.1+ TIA Bill Barker wrote: The 'admin' Context in 3.3.x is similar tothe 'manager' Context in 4.1.x. There are big difference when you get down to the specifics (e.g. 3.3 doesn't include Ant tasks), but in Big Picture terms, they do much the same thing from the HTML interface. [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi All. I'm on TC404, looking at manager configuration. Is Administration Tool only available in TC3.x? Is the Manager Applicatio only available in TC4.1+? Seems like TC404 is somewhere in between. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Bit confused: Admin Tool vs Manager Application
Hi All. I'm on TC404, looking at manager configuration. Is Administration Tool only available in TC3.x? Is the Manager Applicatio only available in TC4.1+? Seems like TC404 is somewhere in between. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bit confused: Admin Tool vs Manager Application
The 'admin' Context in 3.3.x is similar tothe 'manager' Context in 4.1.x. There are big difference when you get down to the specifics (e.g. 3.3 doesn't include Ant tasks), but in Big Picture terms, they do much the same thing from the HTML interface. [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi All. I'm on TC404, looking at manager configuration. Is Administration Tool only available in TC3.x? Is the Manager Applicatio only available in TC4.1+? Seems like TC404 is somewhere in between. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Manager Application and catalina.policy?
H Does HttpConnector have to be enabled on some port e.g. 8080 to use Manager Application ? I am happy with just Ajp at the moment. I am on TC4.0.x and it is not possible to upgrade to TC4.1.x at the moment. Cheers :-) Shapira, Yoav wrote: Howdy, No, you're not right. The two provide different views of security. Httpd.conf controls apache, not tomcat, and does nothing to prevent, for example, the execution of malicious applets. Catalina.policy or whatever you want to call the policy file is used by the JVM security manager to enforce its policies, including for example applet sandboxing. If you're not clear what the security manager does, read up the JDK documentation for it. If should use them both if you're concerned about security. Yoav Shapira Millennium ChemInformatics -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 26, 2003 12:14 AM To: [EMAIL PROTECTED] Subject: No need for catalina.policy? Hi Please tell me once more. Am I right in assumng that I don't really need catalina.policy if I use httpd.conf to control access ? If t, how do they interact ? TIA :-) This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Is it posible to Start and Stop a single web application on local server without using the Manager application
It would be convenient to be able to control each web application in automatic deployment/update routines from ANT or other shell scripts executing locally. When using Apache webserver and mod_webapp to map virtual hosts to webapps, the usage of the Tomcat Manager application seem to be unsupported? Something like this would be nice: ./catalina stop_app myapp ./catalina start_app myapp Ove - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is it posible to Start and Stop a single web application on local server without using the Manager application
Don't use mod_webapp. Contact the Tomcat Manager on port 8080 (use :8080 in your URL), and avoid Apache entirely. John On Mon, 14 Jul 2003 21:25:35 +0200, Ove Heimark [EMAIL PROTECTED] wrote: It would be convenient to be able to control each web application in automatic deployment/update routines from ANT or other shell scripts executing locally. When using Apache webserver and mod_webapp to map virtual hosts to webapps, the usage of the Tomcat Manager application seem to be unsupported? Something like this would be nice: ./catalina stop_app myapp ./catalina start_app myapp Ove - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Is it posible to Start and Stop a single web application on local server without using the Manager application
Will I be able to control all the webapps mounted with Apache/mod_web app from this single Manager webapp using Tomcat native http connector on port 8080? -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: 14. juli 2003 21:28 To: Tomcat Users List Subject: Re: Is it posible to Start and Stop a single web application on local server without using the Manager application Don't use mod_webapp. Contact the Tomcat Manager on port 8080 (use :8080 in your URL), and avoid Apache entirely. John On Mon, 14 Jul 2003 21:25:35 +0200, Ove Heimark [EMAIL PROTECTED] wrote: It would be convenient to be able to control each web application in automatic deployment/update routines from ANT or other shell scripts executing locally. When using Apache webserver and mod_webapp to map virtual hosts to webapps, the usage of the Tomcat Manager application seem to be unsupported? Something like this would be nice: ./catalina stop_app myapp ./catalina start_app myapp Ove - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is it posible to Start and Stop a single web application on local server without using the Manager application
I don't use mod_webapp. If you are contacting Tomcat's manager on port 8080, Tomcat will behave according to the host header (host name) used in the URL. If there's a web app under that host name and everything else is correct (permissions, etc.) then you can manage the web app. John On Mon, 14 Jul 2003 21:34:48 +0200, Ove Heimark [EMAIL PROTECTED] wrote: Will I be able to control all the webapps mounted with Apache/mod_web app from this single Manager webapp using Tomcat native http connector on port 8080? -Original Message- From: John Turner [mailto:[EMAIL PROTECTED] Sent: 14. juli 2003 21:28 To: Tomcat Users List Subject: Re: Is it posible to Start and Stop a single web application on local server without using the Manager application Don't use mod_webapp. Contact the Tomcat Manager on port 8080 (use :8080 in your URL), and avoid Apache entirely. John On Mon, 14 Jul 2003 21:25:35 +0200, Ove Heimark [EMAIL PROTECTED] wrote: It would be convenient to be able to control each web application in automatic deployment/update routines from ANT or other shell scripts executing locally. When using Apache webserver and mod_webapp to map virtual hosts to webapps, the usage of the Tomcat Manager application seem to be unsupported? Something like this would be nice: ./catalina stop_app myapp ./catalina start_app myapp Ove - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Is it posible to Start and Stop a single web application on local server without using the Manager application
I don't use mod_webapp. If you are contacting Tomcat's manager on port 8080, Tomcat will behave according to the host header (host name) used in the URL. If there's a web app under that host name and everything else is correct (permissions, etc.) then you can manage the web app. This is not the case, every webapp maps to a different url, these virtual hostnames are defined in the apache httpd.conf file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is it posible to Start and Stop a single web application on local server without using the Manager application
Reason #953 why you shouldn't use mod_webapp. My point is simple: if it is a separate web application, and it is working, then it should be accessible via the Tomcat Manager application. There is no reason whatsoever to involve Apache or mod_webapp if doing so is causing you grief. Just talk to Tomcat directly. What URL you need to use to do so, and what other things you have to do to get Tomcat's Manager to understand your virtual host setup are up to you...if the Manager app didn't work with multiple virtual hosts and multiple web applications, there'd be no point in having it, would there? That said, you could even modify your own catalina.sh script to issue the commands as necessary, but asking for the dev team to change catalina.sh as you suggested would probably be met with some resistance, with the answer being use the manager application to stop and start your web applications, that is why it is there. John On Mon, 14 Jul 2003 21:47:03 +0200, Ove Heimark [EMAIL PROTECTED] wrote: I don't use mod_webapp. If you are contacting Tomcat's manager on port 8080, Tomcat will behave according to the host header (host name) used in the URL. If there's a web app under that host name and everything else is correct (permissions, etc.) then you can manage the web app. This is not the case, every webapp maps to a different url, these virtual hostnames are defined in the apache httpd.conf file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is it posible to Start and Stop a single web application on local server without using the Manager application
The problem you are experiencing is caused by mod_webapp's configuration peculiarities, not by any deficiency in Tomcat or the Tomcat Manager app. Since mod_webapp is no longer actively developed, my guess is you will have to develop a workaround on your own if it is causing you problems. I suggest contacting Tomcat directly on port 8080 as the workaround. John On Mon, 14 Jul 2003 21:47:03 +0200, Ove Heimark [EMAIL PROTECTED] wrote: I don't use mod_webapp. If you are contacting Tomcat's manager on port 8080, Tomcat will behave according to the host header (host name) used in the URL. If there's a web app under that host name and everything else is correct (permissions, etc.) then you can manage the web app. This is not the case, every webapp maps to a different url, these virtual hostnames are defined in the apache httpd.conf file. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Manager application.
Found my solution myself by doing a simple test. The app. is held in memory and therefore when you reboot the server the changes are lost. Andoni. - Original Message - From: Andoni [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, March 20, 2003 6:39 PM Subject: Manager application. Hello, I am using Tomcat 4.0.4 and the manager application to upload .war files. This works fine. The question I have is where are my files being uploaded to? as I don't see them in the webapps directory of the remote server. Also, if it is being held in memory some how then when I restart Tomcat will my new .war file still be there? My thanks in advance, Andoni. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Manager application.
Hello, I am using Tomcat 4.0.4 and the manager application to upload .war files. This works fine. The question I have is where are my files being uploaded to? as I don't see them in the webapps directory of the remote server. Also, if it is being held in memory some how then when I restart Tomcat will my new .war file still be there? My thanks in advance, Andoni. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
installing war file using manager application
I'm trying to use the manager application to install a war file and I can't figure out what to put in the three fields that show up on the web page. I have created admin and manager roles, and an account for myself that has both these roles. I'm trying to install the struts documentation was file. In Tomcat 3.x, I would have just copied the war file to the webapps directory. After I send this message I'm about to go try that with my 4.1.18 installation. Still, I'd like to know what I'm doing wrong. It sure LOOKS like it should be simple. Attempt one: Path: /struts-documentation Config URL: (empty) WAR URL: file:///opt/struts/webapps/struts-documentation.war Result: FAIL - Encountered exception java.net.MalformedURLException: no protocol: Attempt two: Path: /struts-documentation Config URL: http://localhost:8080/manager WAR URL: file:///opt/struts/webapps/struts-documentation.war Result: FAIL - Encountered exception java.io.IOException: java.io.IOException: Server returned HTTP response code: 401 for URL: http://localhost:8080/manager Attempt three: Entered the following URL directly in the browser: http://localhost:8080/manager/html/install?path=/struts-documentationwar=jar:file:/opt/struts/webapps/struts-documentation.war Result: FAIL - Invalid context path null was specified Help! Thanks, Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
HTML Manager Application FAIL - Invalid application URL was specified
Hi all, First, the preamble: Tomcat 4.1.12, Windows 2k. I've searched the archives to no avail. I've had a million monkeys typing in URLs without success. I've even read the documentation, but that didn't help. Can anybody tell me the magic combination that I need to type into either the Config URL or the WAR URL ? (Can somebody confirm that Config URL = context.xml URL ?) WAR works for a foo.war and an unpacked foo.war so I guess that's the only choice left. I suspect the HTML Manager App is broken because after it whines at me (or my monkeys) for what was typed in I can edit the URL in the browser and generate a line that is valid and actually install my web application. Here's how I can make it work... 1. Path: /hello Config URL: [ empty ] WAR URL: file:c:\devel\jon\hello\build Results in : FAIL - Encountered exception java.net.MalformedURLException: no protocol: 2. Edit the browser URL and remove the installConfig= Results in : OK - Installed application at context path /hello So, broken, or is there some magic that I'm missing. Please hurry, my monkeys are getting tired and I suspect they will faint from hunger before getting the right combination. ;-) Cheers, -- jon -- Jon Eaves [EMAIL PROTECTED] http://www.eaves.org/jon/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Manager application - quick question
Hi all, I'll deploy the manager application to my users. Probably the only funcionality I'll let them use is to stop and start their web applications. Which is the safest method ? - reload ? - stop / start ? - indifferent ? Thanks Renato. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Manager application - quick question
both are safe. reload will be faster(one command vs two), but start/stop will allow web.xml to be read again. Charlie -Original Message- From: Renato [mailto:[EMAIL PROTECTED]] Sent: Monday, November 18, 2002 1:30 PM To: [EMAIL PROTECTED] Subject: Manager application - quick question Hi all, I'll deploy the manager application to my users. Probably the only funcionality I'll let them use is to stop and start their web applications. Which is the safest method ? - reload ? - stop / start ? - indifferent ? Thanks Renato. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat 4.0.6 and manager application problem
Sorry my previous posting didn't have the accurate title. When I tried to logon to Tomcat's manager application with the user name(dba) password(dba) defined in /conf/tomact-users.xml I get the following message. And my browser displayed : HTTP 500 - Internal server error What are the possible causes of the problem ? 2002-11-03 16:25:27 HttpProcessor[1284][4] process.invoke java.lang.ArrayIndexOutOfBoundsException at org.apache.catalina.util.Base64.decode(Base64.java:288) at org.apache.catalina.authenticator.BasicAuthenticator.parseUsername(BasicAuthenticator.java:201) at org.apache.catalina.authenticator.BasicAuthenticator.authenticate(BasicAuthenticator.java:159) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506) .etc my /conf/tomact-users.xml : tomcat-users user name=tomcat password=tomcat roles=tomcat / user name=role1 password=tomcat roles=role1 / user name=both password=tomcat roles=tomcat,role1 / user name=dba password=dba roles=manager / /tomcat-users Joseph __ Yahoo! - We Remember 9-11: A tribute to the more than 3,000 lives lost http://dir.remember.yahoo.com/tribute -- To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Manager application and JDBCRealm
Hello, Is the Manager application that comes with Tomcat supposed be used with the MemoryRealm only, or can it be used with other types of realms, in particular, the JDBCRealm? If it can be used with the JDBCRealm, how does one configure the JDBCRealm to store the additional descriptive information displayed by the Manager application (i.e., Full name for each User and Description for each Group and for each Role) ? The example JDBCRealm configuration that comes with Tomcat does not have a place to store the additional descriptive information . Any help, tips or references to resources appreciated. Thanks, -Brian !-- example has no Description or Full name table/columns -- Realm className=org.apache.catalina.realm.JDBCRealm debug=99 driverName=org.gjt.mm.mysql.Driver connectionURL=jdbc:mysql://localhost:3306/test connectionName=trial connectionPassword=pw userTable=users userNameCol=user_name userCredCol=user_pass userRoleTable=user_roles roleNameCol=role_name /
RE: Manager application and JDBCRealm
You can configure them to work with any realm. If you don't want them to use the default realm in server.xml edit manager.xml and admin.xml and place your realm configuration here. Regards Jim. -Original Message- From: Brian Buckley [mailto:[EMAIL PROTECTED]] Sent: 04 October 2002 13:34 To: [EMAIL PROTECTED] Subject: Manager application and JDBCRealm Hello, Is the Manager application that comes with Tomcat supposed be used with the MemoryRealm only, or can it be used with other types of realms, in particular, the JDBCRealm? If it can be used with the JDBCRealm, how does one configure the JDBCRealm to store the additional descriptive information displayed by the Manager application (i.e., Full name for each User and Description for each Group and for each Role) ? The example JDBCRealm configuration that comes with Tomcat does not have a place to store the additional descriptive information . Any help, tips or references to resources appreciated. Thanks, -Brian !-- example has no Description or Full name table/columns -- Realm className=org.apache.catalina.realm.JDBCRealm debug=99 driverName=org.gjt.mm.mysql.Driver connectionURL=jdbc:mysql://localhost:3306/test connectionName=trial connectionPassword=pw userTable=users userNameCol=user_name userCredCol=user_pass userRoleTable=user_roles roleNameCol=role_name / PLEASE READ: The information contained in this email is confidential and intended for the named recipient(s) only. If you are not an intended recipient of this email you must not copy, distribute or take any further action in reliance on it and you should delete it and notify the sender immediately. Email is not a secure method of communication and Nomura International plc cannot accept responsibility for the accuracy or completeness of this message or any attachment(s). Please examine this email for virus infection, for which Nomura International plc accepts no responsibility. If verification of this email is sought then please request a hard copy. Unless otherwise stated any views or opinions presented are solely those of the author and do not represent those of Nomura International plc. This email is intended for informational purposes only and is not a solicitation or offer to buy or sell securities or related financial instruments. Nomura International plc is regulated by the Financial Services Authority and is a member of the London Stock Exchange. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Manager application and JDBCRealm
Hello, Is the Manager application that comes with Tomcat for use with the MemoryRealm only, or can it be used with other types of realms, in particular, the JDBCRealm? If it can be used with the JDBCRealm, how does one configure the JDBCRealm to store the additional descriptive information displayed by the Manager application (i.e., Full name for each User and Description for each Group and for each Role) ? The example JDBCRealm configuration that comes with Tomcat does not have a place to store the additional descriptive information . Any help, tips or references to resources appreciated. Thanks, -Brian !-- example has no Description or Full name table/columns -- Realm className=org.apache.catalina.realm.JDBCRealm debug=99 driverName=org.gjt.mm.mysql.Driver connectionURL=jdbc:mysql://localhost:3306/test connectionName=trial connectionPassword=pw userTable=users userNameCol=user_name userCredCol=user_pass userRoleTable=user_roles roleNameCol=role_name / -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: web.xml and manager application
Hi, Not sure what this would be, permissions? Have a look at: http://your IP:port/tomcat-docs/manager-howto.html If this doesn't help, send the command, directory of webapp, etc... and I'll see if there is anything wrong. I'm not sure if 4.0.1 is different from 4.0.4 where the manager is concerned, so if the docs are different go with the docs. Alternatively update to 4.0.4 :) Regards, Wm. At 19:03 20/09/2002, you wrote: Hi, If the webapp is just in a directory _not_ packaged as a .war file then use: http://localhost:8080/manager/install?path=/myAppwar=file:/path/to/myApp thanks for your answere. Well it is not working with me I am getting an error: FAIL - Encountered exception java.lang.IllegalArgumentException: Cannot access document base directory /usr/lib/jakarta-tomcat-4.0.1/webapp/wwa-m thanks, Rainer -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 19/09/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 19/09/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
web.xml and manager application
Hi, using Tomcat 4.0.1 on a Linux Box (SuSE 7.3) with JDK 1.3.1. When I change the web.xml of a webapp and want to reload that webapp using the manager application the web.xml-file is not parsed again. Only when I restart the container. Is that normal? Is there a soulution? It is quite unhandy! thanks, rainer
Re: web.xml and manager application
Hi, I had this on 4.0.4. The way I got around it was: (1) Undeploy the wepapp - http://localhost:8080/manager/remove?path=/myApp (2) Delpoy the webapp - http://localhost:8080/manager/install?path=/myAppwar=file:/path/to/myApp This seemed to reparse the web.xml file OK. Reagards, Wm. At 12:29 20/09/2002, you wrote: Hi, using Tomcat 4.0.1 on a Linux Box (SuSE 7.3) with JDK 1.3.1. When I change the web.xml of a webapp and want to reload that webapp using the manager application the web.xml-file is not parsed again. Only when I restart the container. Is that normal? Is there a soulution? It is quite unhandy! thanks, rainer --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 19/09/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 19/09/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: web.xml and manager application
just use stop and start. That will read the web.xml Charlie -Original Message- From: William Wragg [mailto:[EMAIL PROTECTED]] Sent: Friday, September 20, 2002 10:15 AM To: Tomcat Users List Subject: Re: web.xml and manager application Hi, I had this on 4.0.4. The way I got around it was: (1) Undeploy the wepapp - http://localhost:8080/manager/remove?path=/myApp (2) Delpoy the webapp - http://localhost:8080/manager/install?path=/myAppwar=file:/pa th/to/myApp This seemed to reparse the web.xml file OK. Reagards, Wm. At 12:29 20/09/2002, you wrote: Hi, using Tomcat 4.0.1 on a Linux Box (SuSE 7.3) with JDK 1.3.1. When I change the web.xml of a webapp and want to reload that webapp using the manager application the web.xml-file is not parsed again. Only when I restart the container. Is that normal? Is there a soulution? It is quite unhandy! thanks, rainer --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 19/09/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: web.xml and manager application
Hi Charlie, thanks for qour answere! I tested it an with my Tomcat (4.0.1 if it depends on?) the web.xml ist not beeing parsed again. Rainer just use stop and start. That will read the web.xml Charlie -Original Message- From: William Wragg [mailto:[EMAIL PROTECTED]] Sent: Friday, September 20, 2002 10:15 AM To: Tomcat Users List Subject: Re: web.xml and manager application Hi, I had this on 4.0.4. The way I got around it was: (1) Undeploy the wepapp - http://localhost:8080/manager/remove?path=/myApp (2) Delpoy the webapp - http://localhost:8080/manager/install?path=/myAppwar=file:/pa th/to/myApp This seemed to reparse the web.xml file OK. Reagards, Wm. At 12:29 20/09/2002, you wrote: Hi, using Tomcat 4.0.1 on a Linux Box (SuSE 7.3) with JDK 1.3.1. When I change the web.xml of a webapp and want to reload that webapp using the manager application the web.xml-file is not parsed again. Only when I restart the container. Is that normal? Is there a soulution? It is quite unhandy! thanks, rainer --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 19/09/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: web.xml and manager application
Hi, I cannot install the Webapp with the manager app since it is not a .war. Do you know if there is a way? If I only try: http://localhost:8080/manager/install?path=/myApp I am getting a FAIL - Invalid application URL null was specified message. thanks, Rainer Hi, I had this on 4.0.4. The way I got around it was: (1) Undeploy the wepapp - http://localhost:8080/manager/remove?path=/myApp (2) Delpoy the webapp - http://localhost:8080/manager/install?path=/myAppwar=file:/path/to/myApp This seemed to reparse the web.xml file OK. Reagards, Wm. At 12:29 20/09/2002, you wrote: Hi, using Tomcat 4.0.1 on a Linux Box (SuSE 7.3) with JDK 1.3.1. When I change the web.xml of a webapp and want to reload that webapp using the manager application the web.xml-file is not parsed again. Only when I restart the container. Is that normal? Is there a soulution? It is quite unhandy! thanks, rainer --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 19/09/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 19/09/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: web.xml and manager application
Hi, If the webapp is just in a directory _not_ packaged as a .war file then use: http://localhost:8080/manager/install?path=/myAppwar=file:/path/to/myApp If the webapp is packaged as a .war file use: http://localhost:8080/manager/install?path=/myAppwar=jar:/path/to/myApp.war!/ Hope this helps, Wm. At 17:22 20/09/2002, you wrote: Hi, I cannot install the Webapp with the manager app since it is not a .war. Do you know if there is a way? If I only try: http://localhost:8080/manager/install?path=/myApp I am getting a FAIL - Invalid application URL null was specified message. thanks, Rainer Hi, I had this on 4.0.4. The way I got around it was: (1) Undeploy the wepapp - http://localhost:8080/manager/remove?path=/myApp (2) Delpoy the webapp - http://localhost:8080/manager/install?path=/myAppwar=file:/path/to/myApp This seemed to reparse the web.xml file OK. Reagards, Wm. At 12:29 20/09/2002, you wrote: Hi, using Tomcat 4.0.1 on a Linux Box (SuSE 7.3) with JDK 1.3.1. When I change the web.xml of a webapp and want to reload that webapp using the manager application the web.xml-file is not parsed again. Only when I restart the container. Is that normal? Is there a soulution? It is quite unhandy! thanks, rainer --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 19/09/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 19/09/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 19/09/2002 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.391 / Virus Database: 222 - Release Date: 19/09/2002 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: web.xml and manager application
Hi, If the webapp is just in a directory _not_ packaged as a .war file then use: http://localhost:8080/manager/install?path=/myAppwar=file:/path/to/myApp thanks for your answere. Well it is not working with me I am getting an error: FAIL - Encountered exception java.lang.IllegalArgumentException: Cannot access document base directory /usr/lib/jakarta-tomcat-4.0.1/webapp/wwa-m thanks, Rainer -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat Manager Application and Apache
Hi, is it possible, that the Tomcat Manager Application only works for Tomcat Standalone? I connected Tomcat and Apache and worked with the manager application. I was not able to access the installed web applications without explicitly directing the browser to port 8080. If I want to work with both servers do I have to publish my project always using context path entry? Or is there a way to configure the manager application? Cheers, Nick -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
deploying a new application using /manager - application could notbe started
Hi, I am trying to deploy a application (jcvslet). So, I took the following actions: 1. Installing the application -- in : http://localhost/manager/install?path=/jcvsletwar=jar:file:///C:/Program%20Files/Apache%20Tomcat%204.0/war/jcvslet.war!/ out: OK - Installed application at context path /jcvslet 2. Checking the installation - in : http://localhost/manager/list out: OK - Listed applications for virtual host localhost /manager:running:0 /examples:running:0 /jcvslet:stopped:0 /tomcat-docs:running:0 /webdav:running:0 /eDoc:running:0 /test:running:0 /:running:0 3. Starting the application in : http://localhost/manager/start?path=/jcvslet out: FAIL - Application at context path /jcvslet could not be started --- I did not find anything neither in the logs nor in the archives that could explain that. Any idea ? Thanks in advance, Joao Macaiba. -- From The Practice Programming by Brian W Kernighan Rob Pike: Another effective [debugging] technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes it takes no more than a few sentences, followed by an embarrassed Never mind. I see what's wrong. Sorry to bother you. This works remarkbly well; you can even use non-programmers as listeners. One university computer center kept a teddy bear near the help desk. Students with mysterious bugs were required to explain them to the bear before they could speak to a human counselor. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: deploying a new application using /manager - application couldnot be started
Installing an application automatically starts it -- you don't need to do that separately. The only reason you'd need start is if you did a stop. Craig On Wed, 10 Jul 2002, João Luiz de Brito Macaíba wrote: Date: Wed, 10 Jul 2002 17:38:44 -0300 (EST) From: João Luiz de Brito Macaíba [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: deploying a new application using /manager - application could not be started Hi, I am trying to deploy a application (jcvslet). So, I took the following actions: 1. Installing the application -- in : http://localhost/manager/install?path=/jcvsletwar=jar:file:///C:/Program%20Files/Apache%20Tomcat%204.0/war/jcvslet.war!/ out: OK - Installed application at context path /jcvslet 2. Checking the installation - in : http://localhost/manager/list out: OK - Listed applications for virtual host localhost /manager:running:0 /examples:running:0 /jcvslet:stopped:0 /tomcat-docs:running:0 /webdav:running:0 /eDoc:running:0 /test:running:0 /:running:0 3. Starting the application in : http://localhost/manager/start?path=/jcvslet out: FAIL - Application at context path /jcvslet could not be started --- I did not find anything neither in the logs nor in the archives that could explain that. Any idea ? Thanks in advance, Joao Macaiba. -- From The Practice Programming by Brian W Kernighan Rob Pike: Another effective [debugging] technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes it takes no more than a few sentences, followed by an embarrassed Never mind. I see what's wrong. Sorry to bother you. This works remarkbly well; you can even use non-programmers as listeners. One university computer center kept a teddy bear near the help desk. Students with mysterious bugs were required to explain them to the bear before they could speak to a human counselor. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: deploying a new application using /manager - application couldnot be started
Hi Craig, Historians believe that in 2002-07-10 Craig R. McClanahan wrote: Installing an application automatically starts it -- you don't need to do that separately. The only reason you'd need start is if you did a stop. Craig I only tried to *start* it because after I installed the application I noticed that it was *stopped*. I found nothing about that in the logs. :( regards, Macaíba. On Wed, 10 Jul 2002, João Luiz de Brito Macaíba wrote: Date: Wed, 10 Jul 2002 17:38:44 -0300 (EST) From: João Luiz de Brito Macaíba [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: deploying a new application using /manager - application could not be started Hi, I am trying to deploy a application (jcvslet). So, I took the following actions: 1. Installing the application -- in : http://localhost/manager/install?path=/jcvsletwar=jar:file:///C:/Program%20Files/Apache%20Tomcat%204.0/war/jcvslet.war!/ out: OK - Installed application at context path /jcvslet 2. Checking the installation - in : http://localhost/manager/list out: OK - Listed applications for virtual host localhost /manager:running:0 /examples:running:0 /jcvslet:stopped:0 /tomcat-docs:running:0 /webdav:running:0 /eDoc:running:0 /test:running:0 /:running:0 3. Starting the application in : http://localhost/manager/start?path=/jcvslet out: FAIL - Application at context path /jcvslet could not be started --- I did not find anything neither in the logs nor in the archives that could explain that. Any idea ? Thanks in advance, Joao Macaiba. -- From The Practice Programming by Brian W Kernighan Rob Pike: Another effective [debugging] technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes it takes no more than a few sentences, followed by an embarrassed Never mind. I see what's wrong. Sorry to bother you. This works remarkbly well; you can even use non-programmers as listeners. One university computer center kept a teddy bear near the help desk. Students with mysterious bugs were required to explain them to the bear before they could speak to a human counselor. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- From The Practice Programming by Brian W Kernighan Rob Pike: Another effective [debugging] technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes it takes no more than a few sentences, followed by an embarrassed Never mind. I see what's wrong. Sorry to bother you. This works remarkbly well; you can even use non-programmers as listeners. One university computer center kept a teddy bear near the help desk. Students with mysterious bugs were required to explain them to the bear before they could speak to a human counselor. ** | .''`. | Debian GNU/Linux: http://www.debian.org| | : :' : | Debian BR...: http://debian-br.sourceforge.net | | `. `'` | | | `-| Be Happy! Be FREE! | ** -- João Macaíba Serviço de Suporte a Informações +55 21 2274.7445Rede Nacional de Ensino e Pesquisa http://www.rnp.br -- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: deploying a new application using /manager - application couldnot be started
On Wed, 10 Jul 2002, João Luiz de Brito Macaíba wrote: Date: Wed, 10 Jul 2002 17:52:05 -0300 (EST) From: João Luiz de Brito Macaíba [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: deploying a new application using /manager - application could not be started Hi Craig, Historians believe that in 2002-07-10 Craig R. McClanahan wrote: Installing an application automatically starts it -- you don't need to do that separately. The only reason you'd need start is if you did a stop. Craig I only tried to *start* it because after I installed the application I noticed that it was *stopped*. I found nothing about that in the logs. :( The only reason it would be stopped after an install is if there were some problem during startup (such as a parsing error on web.xml, a missing servlet class, or something like that). Check the log files for more info on what went wrong. regards, Macaíba. Craig On Wed, 10 Jul 2002, João Luiz de Brito Macaíba wrote: Date: Wed, 10 Jul 2002 17:38:44 -0300 (EST) From: João Luiz de Brito Macaíba [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: deploying a new application using /manager - application could not be started Hi, I am trying to deploy a application (jcvslet). So, I took the following actions: 1. Installing the application -- in : http://localhost/manager/install?path=/jcvsletwar=jar:file:///C:/Program%20Files/Apache%20Tomcat%204.0/war/jcvslet.war!/ out: OK - Installed application at context path /jcvslet 2. Checking the installation - in : http://localhost/manager/list out: OK - Listed applications for virtual host localhost /manager:running:0 /examples:running:0 /jcvslet:stopped:0 /tomcat-docs:running:0 /webdav:running:0 /eDoc:running:0 /test:running:0 /:running:0 3. Starting the application in : http://localhost/manager/start?path=/jcvslet out: FAIL - Application at context path /jcvslet could not be started --- I did not find anything neither in the logs nor in the archives that could explain that. Any idea ? Thanks in advance, Joao Macaiba. -- From The Practice Programming by Brian W Kernighan Rob Pike: Another effective [debugging] technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes it takes no more than a few sentences, followed by an embarrassed Never mind. I see what's wrong. Sorry to bother you. This works remarkbly well; you can even use non-programmers as listeners. One university computer center kept a teddy bear near the help desk. Students with mysterious bugs were required to explain them to the bear before they could speak to a human counselor. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- From The Practice Programming by Brian W Kernighan Rob Pike: Another effective [debugging] technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes it takes no more than a few sentences, followed by an embarrassed Never mind. I see what's wrong. Sorry to bother you. This works remarkbly well; you can even use non-programmers as listeners. One university computer center kept a teddy bear near the help desk. Students with mysterious bugs were required to explain them to the bear before they could speak to a human counselor. ** | .''`. | Debian GNU/Linux: http://www.debian.org| | : :' : | Debian BR...: http://debian-br.sourceforge.net | | `. `'` | | | `-| Be Happy! Be FREE! | ** -- João Macaíba Serviço de Suporte a Informações +55 21 2274.7445Rede Nacional de Ensino e Pesquisa http://www.rnp.br -- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED
deploying a new application using /manager - application could notbe started
Hi, I am trying to deploy a application (jcvslet). So, I took the following actions: 1. Installing the application -- in : http://localhost/manager/install?path=/jcvsletwar=jar:file:///C:/Program%20Files/Apache%20Tomcat%204.0/war/jcvslet.war!/ out: OK - Installed application at context path /jcvslet 2. Checking the installation - in : http://localhost/manager/list out: OK - Listed applications for virtual host localhost /manager:running:0 /examples:running:0 /jcvslet:stopped:0 /tomcat-docs:running:0 /webdav:running:0 /eDoc:running:0 /test:running:0 /:running:0 3. Starting the application in : http://localhost/manager/start?path=/jcvslet out: FAIL - Application at context path /jcvslet could not be started --- I did not find anything neither in the logs nor in the archives that could explain that. Any idea ? Thanks in advance, Joao Macaiba. -- From The Practice Programming by Brian W Kernighan Rob Pike: Another effective [debugging] technique is to explain your code to someone else. This will often cause you to explain the bug to yourself. Sometimes it takes no more than a few sentences, followed by an embarrassed Never mind. I see what's wrong. Sorry to bother you. This works remarkbly well; you can even use non-programmers as listeners. One university computer center kept a teddy bear near the help desk. Students with mysterious bugs were required to explain them to the bear before they could speak to a human counselor. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat 4.1/4.0 manager application
On Fri, 14 Jun 2002, Sam Ewing wrote: Date: Fri, 14 Jun 2002 23:07:48 -0700 (PDT) From: Sam Ewing [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: Tomcat 4.1/4.0 manager application Thanks for all the help Craig. A couple of other doubts :-) 1. In Tomcat 4.1, when a install command is run, how is the web application 'installed'. I mean, the application is neither copied into webapps, nor a Context entry added to server.xml; so how does the requests for /new_app (if that is the context path) sent to the new application? Is everything manipulated in the in memory representation of server.xml? Yes, although technically there isn't really any in-memory representation of server.xml contents. Instead, there are the actual Tomcat components, usually one object per XML element in server.xml. For example, there is an object that implements the org.apache.catalina.Host interface for each Host element in server.xml. Each of these components have JavaBeans getters and setters that correspond to the configurable properties in server.xml, so saving server.xml again is primarily an exercise of walking down the tree of components and creating an XML element for each relevant one. (The details are somewhat messier than this, but that's the basic idea.) An application being installed causes the creation of a new Context object in memory, with a docBase property that points at the absolute path to your directory or WAR file. The context path for the new app (i.e. the path property) is immediately added to the mapping tables that Tomcat uses to decide which webapp to give a request to. By the way, the deploy command in 4.1 is similar but different. It uploads the WAR file, unpacks it into a temporary directory, and does (essentially) an install of that temporary directory. The adminisration app in 4.1.x already has the ability to save the current in-memory state of Tomcat's configuration back to server.xml -- it's just a matter of adding the triggering of this save when install executes. 2. In Tomcat 4.0, the remove command doesnt remove the installed app from application base.. is that ok since the remove in 4.0 is actually an undeploy? I don't think you'll see any major functional changes in 4.0.x any more, just bugfix releases. Personally, I'm focused on the 4.1.x version's behavior, since there are tons of new features and performance improvements. 3. In Tomcat 4.0, the install copies the web app into the application base.. yet when I restart Tomcat, the 'manager list' doesnt show this new webapp, nor does is this application accessible. Why is this when the application has been unpacked into application base? The only way I can think of for that to happen would be if an error occurred on your app during the startup -- check the logs. But I don't use 4.0.x any more, so don't remember any more details. Sorry for all the questions! I'm afraid I can't be of much additional assistance, since I'm not actively involved in Tomcat development any more (my job roles have changed, and occupy more than 100% of my time :-). Craig --- Craig R. McClanahan [EMAIL PROTECTED] wrote: On Fri, 14 Jun 2002, Sam Ewing wrote: Date: Fri, 14 Jun 2002 13:00:25 -0700 (PDT) From: Sam Ewing [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Tomcat 4.1/4.0 manager application I'm facing a few problems with the Tomcat manager application.. 1. In 4.0.4, the install command copies the web app into the appBase directory.. in 4.1.3, the install does not do this; however the installed application is availble for use. This is the correct behavior for the future -- it takes advantage of the fact that the docBase property of a context can be an absolute pathname. I use this feature for rapid development (coupled with the custom Ant tasks that talk to the Manager webapp, by installing the output directory of my build process. So, now my development cycle is: (1) ant compile (2) ant install (3) test things (4) fix something (5) ant compile reload (6) goto (3) until its time for a beer (7) ant remove and never have to shut down Tomcat for anything. (The only time you need to do a remove and install again is if you change web.xml - reload only pays attention to updated classes so that it can run faster.) The Application Developer's Guide that comes with 4.1.x explains this, and includes a nice build.xml file to start with. Besides supporting the Ant tasks described above, it automatically sets up your compile classpath to reflect the environment that will be present at runtime (for example, it adds all the JAR files in common/lib and the other shared directories). After restarting Tomcat 4.1, the newly installed application is not visible. Am I doing something
Tomcat 4.1/4.0 manager application
I'm facing a few problems with the Tomcat manager application.. 1. In 4.0.4, the install command copies the web app into the appBase directory.. in 4.1.3, the install does not do this; however the installed application is availble for use. After restarting Tomcat 4.1, the newly installed application is not visible. Am I doing something wrong here? or is it a bug in 4.1? 2. How do you pass the war file to the 4.1 deploy command? The documentation says - Upload the web application archive (WAR) file that is specified as the request data in this HTTP PUT . Umm.. how do I do this via a browser? On another train..what is the difference between what the install and deploy commands do? AFAIK, both seem to be installing and starting the app.. Thanks!!! __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat 4.1/4.0 manager application
My understanding is that everything you see from Install is a feature, not a bug. It's a bit strange, but that's what it's spec'd out to do. The difference with Deploy is that it installs the app permanently. Not sure about how to upload the file through the manager web application. I know you can do it (as well as Install, Reload etc) in 4.1 via one of the new Ant taskdefs.. you might check those out. Sam Ewing java_developer99 To: [EMAIL PROTECTED] @yahoo.com cc: Subject: Tomcat 4.1/4.0 manager application 06/14/2002 03:00 PM Please respond to Tomcat Users List I'm facing a few problems with the Tomcat manager application.. 1. In 4.0.4, the install command copies the web app into the appBase directory.. in 4.1.3, the install does not do this; however the installed application is availble for use. After restarting Tomcat 4.1, the newly installed application is not visible. Am I doing something wrong here? or is it a bug in 4.1? 2. How do you pass the war file to the 4.1 deploy command? The documentation says - Upload the web application archive (WAR) file that is specified as the request data in this HTTP PUT . Umm.. how do I do this via a browser? On another train..what is the difference between what the install and deploy commands do? AFAIK, both seem to be installing and starting the app.. Thanks!!! __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat 4.1/4.0 manager application
On Fri, 14 Jun 2002, Sam Ewing wrote: Date: Fri, 14 Jun 2002 13:00:25 -0700 (PDT) From: Sam Ewing [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Tomcat 4.1/4.0 manager application I'm facing a few problems with the Tomcat manager application.. 1. In 4.0.4, the install command copies the web app into the appBase directory.. in 4.1.3, the install does not do this; however the installed application is availble for use. This is the correct behavior for the future -- it takes advantage of the fact that the docBase property of a context can be an absolute pathname. I use this feature for rapid development (coupled with the custom Ant tasks that talk to the Manager webapp, by installing the output directory of my build process. So, now my development cycle is: (1) ant compile (2) ant install (3) test things (4) fix something (5) ant compile reload (6) goto (3) until its time for a beer (7) ant remove and never have to shut down Tomcat for anything. (The only time you need to do a remove and install again is if you change web.xml - reload only pays attention to updated classes so that it can run faster.) The Application Developer's Guide that comes with 4.1.x explains this, and includes a nice build.xml file to start with. Besides supporting the Ant tasks described above, it automatically sets up your compile classpath to reflect the environment that will be present at runtime (for example, it adds all the JAR files in common/lib and the other shared directories). After restarting Tomcat 4.1, the newly installed application is not visible. Am I doing something wrong here? or is it a bug in 4.1? Saving the updated state (into server.xml) is a feature that is currently still being added -- I think you'll see that finished by 4.1.5. 2. How do you pass the war file to the 4.1 deploy command? The documentation says - Upload the web application archive (WAR) file that is specified as the request data in this HTTP PUT . Umm.. how do I do this via a browser? You don't -- it requires a client program. Simplest way, again, is to use the custom Ant deploy task which does all the nitty gritty for you. You can easily incorporate the execution of this into a shell script. On another train..what is the difference between what the install and deploy commands do? AFAIK, both seem to be installing and starting the app.. Install connects an unpacked directory, or a WAR file, directly to a running Tomcat installation. Because nothing has to be copied, this runs pretty quickly, and is ideal for development. However, the directory or WAR file has to be on the same machine that Tomcat is running on. Deploy lets you run a tool (or Ant script) on a separate computer. It takes longer because of the need to upload the WAR, but you can run it from anywhere, not just the same server. Over time, I expect to see management tools and IDEs incorporate support for using the deploy and undeploy features behind the scenes for you -- it makes for very easy Tomcat application management. Thanks!!! Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Tomcat 4.1/4.0 manager application
Thanks for all the help Craig. A couple of other doubts :-) 1. In Tomcat 4.1, when a install command is run, how is the web application 'installed'. I mean, the application is neither copied into webapps, nor a Context entry added to server.xml; so how does the requests for /new_app (if that is the context path) sent to the new application? Is everything manipulated in the in memory representation of server.xml? 2. In Tomcat 4.0, the remove command doesnt remove the installed app from application base.. is that ok since the remove in 4.0 is actually an undeploy? 3. In Tomcat 4.0, the install copies the web app into the application base.. yet when I restart Tomcat, the 'manager list' doesnt show this new webapp, nor does is this application accessible. Why is this when the application has been unpacked into application base? Sorry for all the questions! --- Craig R. McClanahan [EMAIL PROTECTED] wrote: On Fri, 14 Jun 2002, Sam Ewing wrote: Date: Fri, 14 Jun 2002 13:00:25 -0700 (PDT) From: Sam Ewing [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Tomcat 4.1/4.0 manager application I'm facing a few problems with the Tomcat manager application.. 1. In 4.0.4, the install command copies the web app into the appBase directory.. in 4.1.3, the install does not do this; however the installed application is availble for use. This is the correct behavior for the future -- it takes advantage of the fact that the docBase property of a context can be an absolute pathname. I use this feature for rapid development (coupled with the custom Ant tasks that talk to the Manager webapp, by installing the output directory of my build process. So, now my development cycle is: (1) ant compile (2) ant install (3) test things (4) fix something (5) ant compile reload (6) goto (3) until its time for a beer (7) ant remove and never have to shut down Tomcat for anything. (The only time you need to do a remove and install again is if you change web.xml - reload only pays attention to updated classes so that it can run faster.) The Application Developer's Guide that comes with 4.1.x explains this, and includes a nice build.xml file to start with. Besides supporting the Ant tasks described above, it automatically sets up your compile classpath to reflect the environment that will be present at runtime (for example, it adds all the JAR files in common/lib and the other shared directories). After restarting Tomcat 4.1, the newly installed application is not visible. Am I doing something wrong here? or is it a bug in 4.1? Saving the updated state (into server.xml) is a feature that is currently still being added -- I think you'll see that finished by 4.1.5. 2. How do you pass the war file to the 4.1 deploy command? The documentation says - Upload the web application archive (WAR) file that is specified as the request data in this HTTP PUT . Umm.. how do I do this via a browser? You don't -- it requires a client program. Simplest way, again, is to use the custom Ant deploy task which does all the nitty gritty for you. You can easily incorporate the execution of this into a shell script. On another train..what is the difference between what the install and deploy commands do? AFAIK, both seem to be installing and starting the app.. Install connects an unpacked directory, or a WAR file, directly to a running Tomcat installation. Because nothing has to be copied, this runs pretty quickly, and is ideal for development. However, the directory or WAR file has to be on the same machine that Tomcat is running on. Deploy lets you run a tool (or Ant script) on a separate computer. It takes longer because of the need to upload the WAR, but you can run it from anywhere, not just the same server. Over time, I expect to see management tools and IDEs incorporate support for using the deploy and undeploy features behind the scenes for you -- it makes for very easy Tomcat application management. Thanks!!! Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
id and password for Manager application?
what is id and password for Manager application? thanks, sandeep
RE: id and password for Manager application?
-Original Message- From: Sandeep Contractor [mailto:[EMAIL PROTECTED]] Sent: 31 May 2002 13:16 To: [EMAIL PROTECTED] Subject: id and password for Manager application? what is id and password for Manager application? thanks, sandeep Sandeep You need to create your own - either use the MemoryRealm that Tomcat uses by default, and add your chosen username and password (and role=manager) to tomcat-users.xml in $CATALINA_HOME/conf, or configure and use a JDBC or JNDI realm. HTH, John -- John Niven Please reply through mailing list -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
ajp13 and the manager application
Hi list I'm using tomcat throgh an isapi filter in IIS and the ajp13 Connector. This works fine for all applications except for the manager application. This works only if I call it directly from tomcat. Is this a security problem? Thanks for your help mit freundlichen Grussen Galexis AG Beat Friedli . SW-Entwicklung (DDIS/ASW) Grubenstrasse 11 . CH-3322 Schoenbuehl tel: +41 (0)31 858 72 32 . fax: +41 (0)31 858 78 81 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Please advice: Deploy the manager application
Hi all, I want to deploy the manager application to stop and start different contexts on a multiple Virtual Host environment. I don't want my clients to have direct access to it, just the administrator ( I'm thinking to build a wrapper around it, so it will be transparent for the users to restart their context ). I did some preliminar tests and I have some questions: - Would I have to define the manager application for each Host ? - Would I have to mark all contexts as privileged=true ? - Is their a way to list all the applications, or is it limited on a per- virtual host basis ? Any other recommendation to make the 'manager' available to users ? Thanks !! -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
RE: Please advice: Deploy the manager application
see intermixed -Original Message- From: Renato [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 7:33 AM To: [EMAIL PROTECTED] Subject: Please advice: Deploy the manager application Hi all, I want to deploy the manager application to stop and start different contexts on a multiple Virtual Host environment. I don't want my clients to have direct access to it, just the administrator ( I'm thinking to build a wrapper around it, so it will be transparent for the users to restart their context ). I did some preliminar tests and I have some questions: - Would I have to define the manager application for each Host ? you would have to define your wrapper for each host. It is just another context. - Would I have to mark all contexts as privileged=true ? Only the manager/wrapper context - Is their a way to list all the applications, or is it limited on a per- virtual host basis ? It is limited per virtual host, as manager is a context within a virtual host Any other recommendation to make the 'manager' available to users ? Thanks !! Charlie -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Tomcat Manager Application Questions and Problems
1) Does reload pick up changes to web.xml? 2) I added manager servlet to my web app (/AGCW) and when I send the manager a command to reload I get the following in the localhost_log: 2001-10-22 16:32:34 StandardWrapper[/AGCW:Manager]: Loading container servlet Manager 2001-10-22 16:32:34 Manager: init 2001-10-22 16:32:34 Manager: init: Associated with Deployer 'localhost' 2001-10-22 16:32:34 Manager: restart: Reloading web application at '/AGCW' 2001-10-22 16:32:34 StandardContext[/AGCW]: Reloading this Context has started 2001-10-22 16:32:34 StandardWrapper[/AGCW:Manager]: Waiting for 1 instance(s) to be deallocated and then everything hangs. Is this because the app is trying to restart itself? Do I need to create another app just to do the restart? Sure would be nice if an app could restart itself (e.g., to pick up web.xml or other changes) Frank Lawlor Athens Group, Inc. (512) 345-0600 x151 Athens Group, an employee-owned consulting firm integrating technology strategy and software solutions.
manager application bug
In reading up on the Tomcat Manager Application in the 4.0b5 release, it mentions a bug that has been around since the milestone 2 release. The bug has to do with loading/unloading/reloading of an application via a URL (it's in the documentation for the manager application). Here is the full text of the bug (in case noone has any idea of what I'm talking about): WARNING - As of the Tomcat 4.0 milestone 2 release, there is a bug in the operation of the deploy command that prevents deploying, undeploying, and then redeploying an application from the same URL for a web application archive (WAR) file. To work around this, either redeploy the application from a different WAR file URL, or deploy from an unpacked directory (on the same server that Tomcat is running on). Are there any immediate plans to fix this bug? Ryan
Is there a user interface for /manager application?
Hello, is there a user interface for the /manager application? I only found a description of the URLs for scripting. Thank you Stefan
