Howdy,
Would multiple Tomcat instances be run in a production environment as
well?
Yeah, that's what I meant when I said one webapp per instance. If you
have multiple webapps, that's multiple tomcat instances ;) Of course
you can keep the admin or manager webapps also running on each instance
Howdy,
Would multiple Tomcat instances be run in a production environment as
well?
Yeah, that's what I meant when I said one webapp per instance. If you
have multiple webapps, that's multiple tomcat instances ;) Of course
you can keep the admin or manager webapps also running on each
My personal experience has shown both. Shops that plan for enterprise
wide services tend to get large servers and host multiple webapps on
one container on such machines. This lends itself well to centralized
administration, etc.
Shops that add webapps incrementally or at the departmental levels
My personal experience has shown both. Shops that plan for enterprise
wide services tend to get large servers and host multiple webapps on
one container on such machines. This lends itself well to centralized
administration, etc.
Shops that add webapps incrementally or at the departmental
Everyone I've seen uses one container from one vendor. WebLogic and
WebSphere appear to be fairly popular choices but I've heard of lots of
Tomcat and JBoss usage throughout Texas as well.
--- [EMAIL PROTECTED] wrote:
Thanks for the feedback. :) Do you know if the larger shops tend
to use
Would multiple Tomcat instances be run in a production environment as well?
We're developing a webapp and having to retart Tomcat with each webapp
installation is one of our concerns.
Peace...
Tom
Howdy,
Wow, OK, thanks for the great insight. In other words, it's safe to
assume to always restart Tomcat when deploying webapps. That, of
course, is less than ideal. For testing, that just makes the
development time longer (and more complicated, since now we have to
remember to restart
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Shapira, Yoav wrote:
| Howdy,
|
|
|Wow, OK, thanks for the great insight. In other words, it's safe to
|assume to always restart Tomcat when deploying webapps. That, of
|course, is less than ideal. For testing, that just makes the
|development time
Howdy,
We are running Tomcat 5.0.18 w/ jdk 1.4.2 on Linux. We deploy our wars
with the catalina deployer and ant. We automate our builds and
deployments for every 30 minutes. So, every half an hour we build and
deploy our war to tomcat.
Out of curiosity, why every half hour?
This process
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
|
| Out of curiosity, why every half hour?
Seemed like a good round number. No real reason, we just wanted things
current. :)
|
| So there's a memory leak somewhere.
Yes, no doubt. I'm trying to discover if it's my app (very well could
be) or Tomcat.
Hi!
I don't know if this applies to your webapp, but there is an issue
with the java compiler having a memory leak which can lead to OOM
errors when tomcat has to compile many jsps over and over. A remidy
for this is either to use jikes instead of javac entirely or to set
the fork attribute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Philipp Taprogge wrote:
| Hi!
|
| I don't know if this applies to your webapp, but there is an issue with
| the java compiler having a memory leak which can lead to OOM errors when
| tomcat has to compile many jsps over and over. A remidy for this is
|
Actually, that's not quite correct. From $CATALINA_HOME/RELEASE_NOTES:
JAVAC leaking memory:
The Java compiler leaks memory each time a class is compiled. Web
applications
containing hundreds of JSP files may as a result trigger out of memory
errors
Seth Ladd wrote:
Hello,
We are running Tomcat 5.0.18 w/ jdk 1.4.2 on Linux. We deploy our wars
with the catalina deployer and ant. We automate our builds and
deployments for every 30 minutes. So, every half an hour we build and
deploy our war to tomcat.
This process seems to always force an
Hi!
Josh Rehman wrote:
Note: This issue has been fixed in Sun JDK 1.4.x.
Thanks for pointing out. I thought a fix was implemented only recently
in the latest java version. My mistake obviously.
Phil
-
To unsubscribe,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| There are some problems with certain webapps (Struts based webapps in
| particular).
| http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26135
|
| More generally, there's no way to force the VM to discard a classloader,
| so I think it is unwise to
Seth Ladd wrote:
Wow, OK, thanks for the great insight. In other words, it's safe to
assume to always restart Tomcat when deploying webapps. That, of
course, is less than ideal. For testing, that just makes the
development time longer (and more complicated, since now we have to
remember to
Dear [EMAIL PROTECTED],
We received your message on 1/30/2004 at 6:51:07 PM Central Standard Time.
Thank you for contacting Member Savings. We have received and are reviewing your
inquiry. Due to heavy volume, it may take longer than usual for us to get back to
you. Messages are being
18 matches
Mail list logo
