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
**
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
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
of
this is technically doable right now but it's not easy to do productively.
Gili
--
View this message in context:
http://old.nabble.com/One-process-per-webapp-tp31836121p31851393.html
Sent from the Tomcat - User mailing list archive at Nabble.com
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,
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 as a
-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,
-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 JVM and use
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.
-
To unsubscribe, e-mail: users-unsubscr
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-per-webapp-tp31836121p31846007.html
Sent from the Tomcat - User mailing list archive
this in terms of simple script files.
It's a lot more involved.
Gili
--
View this message in context:
http://old.nabble.com/One-process-per-webapp-tp31836121p31846107.html
Sent from the Tomcat - User mailing list archive at Nabble.com
-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 on improving
-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 blank
-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
this message in context:
http://old.nabble.com/One-process-per-webapp-tp31836121p31847022.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
as an appliance. I'm making regular updates to the library and I
need to restart it quickly to speed up the debugging process.
Gili
--
View this message in context:
http://old.nabble.com/One-process-per-webapp-tp31836121p31847177.html
Sent from the Tomcat - User mailing list archive at Nabble.com
.
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 Nabble.com
-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
...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
--
View this message in context:
http://old.nabble.com/One-process-per-webapp-tp31836121p31839136.html
Sent from the Tomcat - User mailing list archive at Nabble.com
19 matches
Mail list logo
