Re: One process per webapp

2011-06-15 Thread Pid
On 15/06/2011 14:20, cowwoc wrote: > If this functionality was built into Tomcat It wouldn't be built into Tomcat, you're asking for a management application and/or proxy. The first might run inside Tomcat and the second sits in front of it - frequently implemented with Apache HTTPD (mod_proxy, m

Re: One process per webapp

2011-06-15 Thread cowwoc
from the beginning, this is more about ease-of-use and productivity than it is about a technical challenge. All of this is technically "doable" right now but it's not easy to do productively. Gili -- View this message in context: http://old.nabble.co

Re: One process per webapp

2011-06-15 Thread Mladen Turk
On 06/15/2011 02:27 PM, Tim Funk wrote: ** Observations ... Hack, yes ... also very simple to do. This might allow webapps to be reloaded without a problem [depending on the nature of the change.] 2) apache httpd can easily handle the proxy scenario. There are "hacks" and "use that other web se

Re: One process per webapp

2011-06-15 Thread Tim Funk
** Observations ... 1) If relying on native - it might be easiest to place the System.loadLibrary() and its classes in the common classloader. Then use a Valve to call System.loadLibrary() so it's only called once. Hack, yes ... also very simple to do. This might allow webapps to be reloaded witho

Re: One process per webapp

2011-06-15 Thread Federico Fissore
for the record, for this very need, with tomcat 6, we made our own "cloud" of tomcats we have tens of embedded tomcats running each a single webapp and each with its own jvm as needed, we start the same webapp on another server, then switch the front end proxy setting to forward the traffic to

Re: One process per webapp

2011-06-14 Thread cowwoc
apped your JNI library with a REST interface, couldn't you > avoid all this foolishness? > That's precisely what I'm doing :) I still need to be able to redeploy the native library though. Think of the native library + RESTful interface + Tomcat as an "appliance". I'

Re: One process per webapp

2011-06-14 Thread cowwoc
ations, the JVM and the OS conspire to lock certain resources > (usually .jar files) and that can be a problem. > > If you're starting a new instance in parallel, wouldn't you want to do > it from a separate directory anyway? > Good point. We could do that. Gili

Re: One process per webapp

2011-06-14 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gili, (Sorry, your message was structured in a way I didn't expect, so I didn't see the lower portion). On 6/14/2011 3:54 PM, cowwoc wrote: > Chris, I'm asking for a lot more sophistication than simply restarting the > JVM. I'm talking about sticking

Re: One process per webapp

2011-06-14 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gili, On 6/14/2011 3:54 PM, cowwoc wrote: >>> 1. Always bounce Tomcat directly instead of re-loading the webapp > > This is too slow (10-15 seconds) in its current form. If you use the > mechanism I'm proposing restart time is instant (you have a b

Re: One process per webapp

2011-06-14 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gili, On 6/14/2011 3:28 PM, cowwoc wrote: > Christopher Schultz-2 wrote: >> >> Why bother redeploying, then? Instead of doing "ant redeploy", just do >> "ant bounce" or something similar. > > I am running inside Netbeans (remember the focus here is o

Re: One process per webapp

2011-06-14 Thread cowwoc
ld one * We ask the old instance to shut down * Note that traffic moves across instances instantly (without waiting for the old instance to shut down) I wouldn't want to try implementing this in terms of simple script files. It's a lot more involved. Gili -- View

Re: One process per webapp

2011-06-14 Thread cowwoc
ing? > The new leak prevention is great, but last time I checked it couldn't solve 100% of offending libraries/webapps. Running webapps in their own JVM would be a 100% fix without having to resort to any magic/hacks. Gili -- View this message in context: http://old.nabble.com/One-process

Re: One process per webapp

2011-06-14 Thread cowwoc
k of is that the old instance might keep files locked on disk (but I think this is no longer the case with Tomcat 7.x) Gili -- View this message in context: http://old.nabble.com/One-process-per-webapp-tp31836121p31845924.html Sent from the Tomcat - User mailing list archive at Nabble.com. --

Re: One process per webapp

2011-06-14 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pid, On 6/14/2011 9:34 AM, Pid wrote: > On 13/06/2011 22:53, Christopher Schultz wrote: >> >> What "single management interface" are you describing in your >> enhancement comments? The Tomcat manager webapp? It's trivial to run a >> manager in each JV

Re: One process per webapp

2011-06-14 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gili, On 6/13/2011 9:26 PM, cowwoc wrote: > Assuming we simply use one webapp per Tomcat instance I'm still looking > for two changes: > > * Restart the entire JVM on webapp redeploy (to avoid JNI and ClassLoader > problems) Why bother redeploying

Re: One process per webapp

2011-06-14 Thread Pid
On 13/06/2011 22:53, Christopher Schultz wrote: > Gili, > > On 6/13/2011 1:07 PM, cowwoc wrote: >> I posted a RFE at https://issues.apache.org/bugzilla/show_bug.cgi?id=51366 >> asking for the ability to seamlessly deploy webapps into separate JVMs. > > So you want Tomcat to have an option to run

Re: One process per webapp

2011-06-13 Thread cowwoc
Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk32htcACgkQ9CaO5/Lv0PAGJwCaA020eDYhHSRmgVxALLLisG7z > 0zgAn1WDZNd+BRnJVD+C/kKUHh6KtotJ > =o0Md > -END PGP SIGNATURE- > > ----------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For addit

Re: One process per webapp

2011-06-13 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gili, On 6/13/2011 1:07 PM, cowwoc wrote: > I posted a RFE at https://issues.apache.org/bugzilla/show_bug.cgi?id=51366 > asking for the ability to seamlessly deploy webapps into separate JVMs. So you want Tomcat to have an option to run as a supervis

One process per webapp

2011-06-13 Thread cowwoc
chitecture. Please read the proposal and let me know what you think. Thanks, Gili -- View this message in context: http://old.nabble.com/One-process-per-webapp-tp31836121p31836121.html Sent from the Tomcat - User mailing list archive at