Hi Chris,
Current architecture is to share a jar in shared/lib between the main
webapps, an admin webapps and a localhost only management webapps.
This
was originally in Tomcat 3. New architecture will separate each, drop
the management webapps and we'll control contexts via multicasting,
jmx,
and/or servlets.
Any reason to share the JAR instead of weploying it several times?
Memory and disk space are pretty cheap.
We are running on 8 year old Sun Netra boxes and our loaded set takes
up half of the available memory which is less than 1GB. Redeployment
on Tomcat 6.0 will include new boxes. The economy is tough, we've been
waiting for new hardware ... should be soon. Then we can make each
Tomcat pretty generic and each context self contained with its own
instance of our JAR.
One question is whether we will need to share our oracle JAR. We don't
currently use JNDI, we manage the connection pool directly. If we want
to limit the poolsize based on the machine then we need to share.
Otherwise we can allocate smaller pools to each webapps that needs
access. I suppose our results will vary depending on whose JDBC we are
using. Currently we use Oracle 8, but with our refresh will go to
Oracle 10. What do you think?
Thanks.
Regards,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
