Re: possible to define/deploy a context but not start it?
Thanks Konstantin. However, that source code achieves deployment by copying/unpacking a war file to tomcat's webapps directory. What I want to be able to do is already have a context defined, and simply get it deployed/started. I would hope this is possible without resorting to file system operations. On 06/02/2010 01:34 PM, Konstantin Kolinko wrote: 2010/6/2 Jeff Ramin: If anybody has the time and is willing to give this a try, I'd like to know if it's possible to deploy a webapp via JMX/jconsole in either tomcat 5.5.x or 6.0.x. I can't seem to do it, although it's possible I have a configuration problem. Thanks. You may start with http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/manager/ManagerServlet.java?view=markup Best regards, Konstantin Kolinko Jeff Ramin Software Engineer Singlewire Software 2601 W Beltline Hwy #510 Madison, WI 53713 Phone Direct - 608.661.1172 www.singlewire.com - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
2010/6/2 Jeff Ramin : > > If anybody has the time and is willing to give this a try, I'd like to know > if > it's possible to deploy a webapp via JMX/jconsole in either tomcat 5.5.x or > 6.0.x. I can't seem to do it, although it's possible I have a configuration > problem. > > Thanks. > > > On 06/02/2010 11:54 AM, Konstantin Kolinko wrote: >> >> 2010/6/2 Jeff Ramin: >> >>> >>> I've been experimenting some more, and can't seem to find a solution to >>> my >>> situation. >>> Deploying an app via JMX seems to be broken. >>> >> >> The manager webapp uses JMX. So it should be working. >> >> (Maybe not the methods that you are trying to use -- I do not know >> which ones you are trying, but some others). >> You may start with http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/manager/ManagerServlet.java?view=markup Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
If anybody has the time and is willing to give this a try, I'd like to know if it's possible to deploy a webapp via JMX/jconsole in either tomcat 5.5.x or 6.0.x. I can't seem to do it, although it's possible I have a configuration problem. Thanks. On 06/02/2010 11:54 AM, Konstantin Kolinko wrote: 2010/6/2 Jeff Ramin: I've been experimenting some more, and can't seem to find a solution to my situation. Deploying an app via JMX seems to be broken. The manager webapp uses JMX. So it should be working. (Maybe not the methods that you are trying to use -- I do not know which ones you are trying, but some others). Anybody have any ideas, or is this unworkable? I do not know what are those "the WebModule beans" that you mentioned and how they do work, are deployed etc. If the only thing that you need is that the incoming requests are not serviced but are replied with error 503 (as Tomcat 5.5 does) or error 404 (as Tomcat 6 does), you can write a Filter that replies with response.sendError() until it is switched into pass-through state with a JMX call or by other means. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- Jeff Ramin Software Engineer Singlewire Software 2601 W Beltline Hwy #510 Madison, WI 53713 Phone Direct - 608.661.1172 www.singlewire.com - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
On 06/02/2010 11:54 AM, Konstantin Kolinko wrote: I do not know what are those "the WebModule beans" that you mentioned and how they do work, are deployed etc. The WebModule stuff is available through jconsole when an app has been deployed. They can be used to start/stop a web app. However, they don't exist unless the app has been deployed. Unfortunately, deploying implies starting, which I don't want. If the only thing that you need is that the incoming requests are not serviced but are replied with error 503 (as Tomcat 5.5 does) or error 404 (as Tomcat 6 does), you can write a Filter that replies with response.sendError() until it is switched into pass-through state with a JMX call or by other means. Thanks for the idea, but our webapp must not run at all. It does some things upon initialization that I need to prevent from happening, which is why it must not be started. -- Jeff Ramin Software Engineer Singlewire Software 2601 W Beltline Hwy #510 Madison, WI 53713 Phone Direct - 608.661.1172 www.singlewire.com - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
2010/6/2 Jeff Ramin : > > I've been experimenting some more, and can't seem to find a solution to my > situation. > Deploying an app via JMX seems to be broken. The manager webapp uses JMX. So it should be working. (Maybe not the methods that you are trying to use -- I do not know which ones you are trying, but some others). > > Anybody have any ideas, or is this unworkable? > I do not know what are those "the WebModule beans" that you mentioned and how they do work, are deployed etc. If the only thing that you need is that the incoming requests are not serviced but are replied with error 503 (as Tomcat 5.5 does) or error 404 (as Tomcat 6 does), you can write a Filter that replies with response.sendError() until it is switched into pass-through state with a JMX call or by other means. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
When I run jconsole against my tomcat instance, the Catalina/Deployer/localhost/operations/manageApp button is broken. I assume this is the same behavior Charles mentioned below, when he said he was unable to get it to work. No stacktraces or log entries, as it doesn't seem possible from jconsole. Thanks. On 06/02/2010 11:29 AM, Pid wrote: On 02/06/2010 16:28, Jeff Ramin wrote: I've been experimenting some more, and can't seem to find a solution to my situation. Deploying an app via JMX seems to be broken. Anybody have any ideas, or is this unworkable? What did you try and what log messages did you see? Were there any stacktrace errors? If there's a problem, we might be able to fix it if you provide some information. p Thanks. On 06/01/2010 01:20 PM, Caldarale, Charles R wrote: From: Jeff Ramin [mailto:jeff.ra...@singlewire.com] Subject: Re: possible to define/deploy a context but not start it? Yes, I've done this. However, I don't see a way to deploy/start my app. If I start jconsole when starting tomcat like this, the WebModule beans I would use to deploy/start my app are not present. That MBean doesn't get created until an app is deployed. Instead, you should be able to use the Catalina/Deployer MBean (but I haven't gotten it to work yet). This would be an acceptable solution. However, like you experienced, the deployer mBean doesn't seem to deploy my app. As a workaround, you could use the HTTP text interface to the manager webapp. I'm trying to avoid running the manager webapp, if at all possible. Thanks. -- Jeff Ramin Software Engineer Singlewire Software 2601 W Beltline Hwy #510 Madison, WI 53713 Phone Direct - 608.661.1172 www.singlewire.com - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
On 02/06/2010 16:28, Jeff Ramin wrote: > > I've been experimenting some more, and can't seem to find a solution to > my situation. > Deploying an app via JMX seems to be broken. > > Anybody have any ideas, or is this unworkable? What did you try and what log messages did you see? Were there any stacktrace errors? If there's a problem, we might be able to fix it if you provide some information. p > Thanks. > >> On 06/01/2010 01:20 PM, Caldarale, Charles R wrote: >>>> From: Jeff Ramin [mailto:jeff.ra...@singlewire.com] >>>> Subject: Re: possible to define/deploy a context but not start it? >>>> >>>> Yes, I've done this. However, I don't see a way to deploy/start my app. >>>> If I start jconsole when starting tomcat like this, the WebModule beans >>>> I would use to deploy/start my app are not present. >>> That MBean doesn't get created until an app is deployed. Instead, >>> you should be able to use the Catalina/Deployer MBean (but I haven't >>> gotten it to work yet). >> This would be an acceptable solution. However, like you experienced, >> the deployer mBean doesn't >> seem to deploy my app. >> >>>As a workaround, you could use the HTTP text interface to the >>> manager webapp. >> I'm trying to avoid running the manager webapp, if at all possible. >> >> Thanks. >> > > signature.asc Description: OpenPGP digital signature
Re: possible to define/deploy a context but not start it?
I've been experimenting some more, and can't seem to find a solution to my situation. Deploying an app via JMX seems to be broken. Anybody have any ideas, or is this unworkable? Thanks. On 06/01/2010 01:20 PM, Caldarale, Charles R wrote: From: Jeff Ramin [mailto:jeff.ra...@singlewire.com] Subject: Re: possible to define/deploy a context but not start it? Yes, I've done this. However, I don't see a way to deploy/start my app. If I start jconsole when starting tomcat like this, the WebModule beans I would use to deploy/start my app are not present. That MBean doesn't get created until an app is deployed. Instead, you should be able to use the Catalina/Deployer MBean (but I haven't gotten it to work yet). This would be an acceptable solution. However, like you experienced, the deployer mBean doesn't seem to deploy my app. As a workaround, you could use the HTTP text interface to the manager webapp. I'm trying to avoid running the manager webapp, if at all possible. Thanks. -- Jeff Ramin Software Engineer Singlewire Software 2601 W Beltline Hwy #510 Madison, WI 53713 Phone Direct - 608.661.1172 www.singlewire.com - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
On 06/01/2010 01:20 PM, Caldarale, Charles R wrote: From: Jeff Ramin [mailto:jeff.ra...@singlewire.com] Subject: Re: possible to define/deploy a context but not start it? Yes, I've done this. However, I don't see a way to deploy/start my app. If I start jconsole when starting tomcat like this, the WebModule beans I would use to deploy/start my app are not present. That MBean doesn't get created until an app is deployed. Instead, you should be able to use the Catalina/Deployer MBean (but I haven't gotten it to work yet). This would be an acceptable solution. However, like you experienced, the deployer mBean doesn't seem to deploy my app. As a workaround, you could use the HTTP text interface to the manager webapp. I'm trying to avoid running the manager webapp, if at all possible. Thanks. -- Jeff Ramin Software Engineer Singlewire Software 2601 W Beltline Hwy #510 Madison, WI 53713 Phone Direct - 608.661.1172 www.singlewire.com - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: possible to define/deploy a context but not start it?
> From: Jeff Ramin [mailto:jeff.ra...@singlewire.com] > Subject: Re: possible to define/deploy a context but not start it? > > Yes, I've done this. However, I don't see a way to deploy/start my app. > If I start jconsole when starting tomcat like this, the WebModule beans > I would use to deploy/start my app are not present. That MBean doesn't get created until an app is deployed. Instead, you should be able to use the Catalina/Deployer MBean (but I haven't gotten it to work yet). As a workaround, you could use the HTTP text interface to the manager webapp. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
On 06/01/2010 11:46 AM, Caldarale, Charles R wrote: From: Jeff Ramin [mailto:jeff.ra...@singlewire.com] Subject: Re: possible to define/deploy a context but not start it? Deploying a webapplication, though, always starts it. If a webapplication is included as a element in server.xml (usually not recommended), it is always deployed and started when server starts, regardless of deployOnStartup option. Besides the documentation, you may also want to look at the archives of this list. deployOnStartup/autoDeploy were discussed several times. I want to start an application via JMX. Thus, tomcat needs to be running, so that the JMX agent is available. But, I don't want my web application to be available until it gets explicitly started as the result of a JMX invocation of a WebModule bean. Konstantin already gave you the answer: It is possible to turn off auto-deploy (autoDeploy, deployOnStartup), i.e. the webapplication will be present in webapps folder, but it will not be running, nor will it be listed by Tomcat Manager. Deploying a webapplication, though, always starts it. Your best bet is to leave the application _undeployed_ until you're ready for it, then deploy it. Yes, I've done this. However, I don't see a way to deploy/start my app. If I start jconsole when starting tomcat like this, the WebModule beans I would use to deploy/start my app are not present. -- Jeff Ramin Software Engineer Singlewire Software 2601 W Beltline Hwy #510 Madison, WI 53713 Phone Direct - 608.661.1172 www.singlewire.com - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
On 06/01/2010 11:45 AM, Pid wrote: On 01/06/2010 17:36, Jeff Ramin wrote: On 05/29/2010 08:30 AM, Konstantin Kolinko wrote: 2010/5/29 Pid: On 28/05/2010 19:07, Jeff Ramin wrote: Running tomcat 5.5.20. Is there a way to configure tomcat such that it is aware of a webapp (context), but doesn't start it (process requests) when tomcat starts? Kinda. Examine the docs, look at the Host and Context attributes, for 'deployOnStartup', 'autoDeploy' and 'reloadable'. Depending on what you need it might be all-or-nothing situation though. It is possible to turn off auto-deploy (autoDeploy, deployOnStartup), i.e. the webapplication will be present in webapps folder, but it will not be running, nor will it be listed by Tomcat Manager. Deploying a webapplication, though, always starts it. If a webapplication is included as a element in server.xml (usually not recommended), it is always deployed and started when server starts, regardless of deployOnStartup option. Besides the documentation, you may also want to look at the archives of this list. deployOnStartup/autoDeploy were discussed several times. Thanks. I just read the thread from a couple weeks ago regarding autoDeploy and deployOnStartup. I'm still not quite sure I can make tomcat do what I want it to, so let me be explicit... I want to start an application via JMX. Thus, tomcat needs to be running, so that the JMX agent is available. But, I don't want my web application to be available until it gets explicitly started as the result of a JMX invocation of a WebModule bean. Does that make sense? Is this possible? I haven't been able to make it work on my dev machine thus far. If you start with deployOnStartup, autoDeploy, reloadable all configured to false in the app's Host and Context you should be able to start Tomcat without any app deployment taking place. Yes, I've been able to do this. However, given this configuration, the WebModule bean(s) is not available for starting my app via JMX. -- Jeff Ramin Software Engineer Singlewire Software 2601 W Beltline Hwy #510 Madison, WI 53713 Phone Direct - 608.661.1172 www.singlewire.com - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: possible to define/deploy a context but not start it?
> From: Jeff Ramin [mailto:jeff.ra...@singlewire.com] > Subject: Re: possible to define/deploy a context but not start it? > > > Deploying a webapplication, though, always starts it. > > > > If a webapplication is included as a element in server.xml > > (usually not recommended), it is always deployed and started when > > server starts, regardless of deployOnStartup option. > > > > Besides the documentation, you may also want to look at the archives > > of this list. deployOnStartup/autoDeploy were discussed several > > times. > > > I want to start an application via JMX. Thus, tomcat needs to be > running, so that the JMX agent is available. But, I don't want my > web application to be available until it gets explicitly started > as the result of a JMX invocation of a WebModule bean. Konstantin already gave you the answer: > > It is possible to turn off auto-deploy (autoDeploy, deployOnStartup), > > i.e. the webapplication will be present in webapps folder, but it will > > not be running, nor will it be listed by Tomcat Manager. > > > > Deploying a webapplication, though, always starts it. Your best bet is to leave the application _undeployed_ until you're ready for it, then deploy it. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
On 01/06/2010 17:36, Jeff Ramin wrote: > On 05/29/2010 08:30 AM, Konstantin Kolinko wrote: >> 2010/5/29 Pid: >> >>> On 28/05/2010 19:07, Jeff Ramin wrote: >>> Running tomcat 5.5.20. Is there a way to configure tomcat such that it is aware of a webapp (context), but doesn't start it (process requests) when tomcat starts? >>> Kinda. Examine the docs, look at the Host and Context attributes, for >>> 'deployOnStartup', 'autoDeploy' and 'reloadable'. Depending on what you >>> need it might be all-or-nothing situation though. >>> >>> >> It is possible to turn off auto-deploy (autoDeploy, deployOnStartup), >> i.e. the webapplication will be present in webapps folder, but it will >> not be running, nor will it be listed by Tomcat Manager. >> >> Deploying a webapplication, though, always starts it. >> >> If a webapplication is included as a element in server.xml >> (usually not recommended), it is always deployed and started when >> server starts, regardless of deployOnStartup option. >> >> Besides the documentation, you may also want to look at the archives >> of this list. deployOnStartup/autoDeploy were discussed several >> times. >> > > Thanks. I just read the thread from a couple weeks ago regarding autoDeploy > and deployOnStartup. I'm still not quite sure I can make tomcat do what > I want it > to, so let me be explicit... > > I want to start an application via JMX. Thus, tomcat needs to be > running, so that > the JMX agent is available. But, I don't want my web application to be > available > until it gets explicitly started as the result of a JMX invocation of a > WebModule bean. > > Does that make sense? Is this possible? I haven't been able to make it > work on my > dev machine thus far. If you start with deployOnStartup, autoDeploy, reloadable all configured to false in the app's Host and Context you should be able to start Tomcat without any app deployment taking place. Are you able to make this work with a very simple app in a .war file (e.g. one that just contains a single servlet that logs a message on init/destroy/doGet)? N.B. Once it's deployed, you'll have to undeploy it before beginning the test cycle again. p signature.asc Description: OpenPGP digital signature
Re: possible to define/deploy a context but not start it?
On 05/29/2010 08:30 AM, Konstantin Kolinko wrote: 2010/5/29 Pid: On 28/05/2010 19:07, Jeff Ramin wrote: Running tomcat 5.5.20. Is there a way to configure tomcat such that it is aware of a webapp (context), but doesn't start it (process requests) when tomcat starts? Kinda. Examine the docs, look at the Host and Context attributes, for 'deployOnStartup', 'autoDeploy' and 'reloadable'. Depending on what you need it might be all-or-nothing situation though. It is possible to turn off auto-deploy (autoDeploy, deployOnStartup), i.e. the webapplication will be present in webapps folder, but it will not be running, nor will it be listed by Tomcat Manager. Deploying a webapplication, though, always starts it. If a webapplication is included as a element in server.xml (usually not recommended), it is always deployed and started when server starts, regardless of deployOnStartup option. Besides the documentation, you may also want to look at the archives of this list. deployOnStartup/autoDeploy were discussed several times. Thanks. I just read the thread from a couple weeks ago regarding autoDeploy and deployOnStartup. I'm still not quite sure I can make tomcat do what I want it to, so let me be explicit... I want to start an application via JMX. Thus, tomcat needs to be running, so that the JMX agent is available. But, I don't want my web application to be available until it gets explicitly started as the result of a JMX invocation of a WebModule bean. Does that make sense? Is this possible? I haven't been able to make it work on my dev machine thus far. Thanks! -- Jeff Ramin Software Engineer Singlewire Software 2601 W Beltline Hwy #510 Madison, WI 53713 Phone Direct - 608.661.1172 www.singlewire.com - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
Thanks for explaining this, Konstantin - I was wondering about this also. - Jeff On 5/29/10 9:30 AM, Konstantin Kolinko wrote: 2010/5/29 Pid: On 28/05/2010 19:07, Jeff Ramin wrote: Running tomcat 5.5.20. Is there a way to configure tomcat such that it is aware of a webapp (context), but doesn't start it (process requests) when tomcat starts? Kinda. Examine the docs, look at the Host and Context attributes, for 'deployOnStartup', 'autoDeploy' and 'reloadable'. Depending on what you need it might be all-or-nothing situation though. It is possible to turn off auto-deploy (autoDeploy, deployOnStartup), i.e. the webapplication will be present in webapps folder, but it will not be running, nor will it be listed by Tomcat Manager. Deploying a webapplication, though, always starts it. If a webapplication is included as a element in server.xml (usually not recommended), it is always deployed and started when server starts, regardless of deployOnStartup option. Besides the documentation, you may also want to look at the archives of this list. deployOnStartup/autoDeploy were discussed several times. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
2010/5/29 Pid : > On 28/05/2010 19:07, Jeff Ramin wrote: >> >> Running tomcat 5.5.20. >> >> Is there a way to configure tomcat such that it is aware of a webapp >> (context), >> but doesn't start it (process requests) when tomcat starts? > > Kinda. Examine the docs, look at the Host and Context attributes, for > 'deployOnStartup', 'autoDeploy' and 'reloadable'. Depending on what you > need it might be all-or-nothing situation though. > It is possible to turn off auto-deploy (autoDeploy, deployOnStartup), i.e. the webapplication will be present in webapps folder, but it will not be running, nor will it be listed by Tomcat Manager. Deploying a webapplication, though, always starts it. If a webapplication is included as a element in server.xml (usually not recommended), it is always deployed and started when server starts, regardless of deployOnStartup option. Besides the documentation, you may also want to look at the archives of this list. deployOnStartup/autoDeploy were discussed several times. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: possible to define/deploy a context but not start it?
On 28/05/2010 19:07, Jeff Ramin wrote: > > Running tomcat 5.5.20. > > Is there a way to configure tomcat such that it is aware of a webapp > (context), > but doesn't start it (process requests) when tomcat starts? Kinda. Examine the docs, look at the Host and Context attributes, for 'deployOnStartup', 'autoDeploy' and 'reloadable'. Depending on what you need it might be all-or-nothing situation though. p signature.asc Description: OpenPGP digital signature
