On my servers I use Debian etch, Apache 2, java 6, tomcat 5.5, Cocoon
2.1. Formerly I used jetty for production, for quite some years, but
with the latest releases of tomcat, I can't confirm Tobia's
experiences. It seems to me, that more and more good reasons for
preferentially using jetty for production have been dropped with
every new version of jetty and tomcat after v 4.x.
On Nov 27, 2007, at 8:52 AM, Peter Sparkes wrote:
I am using Apache 2, Debian etch, java 1.5, tomcat 5 and Cocoon 2.1
and got the whole thing up and running in under a day. I have very
little experience in setting up such a system so it can't be too
difficult.
I found http://edwardaux.wordpress.com/2006/09/20/3/ very helpful
in setting the system up so that I could host multiple sites.
I think this approach, isn't generally useful. Why do you need
different tomcat instances for every single webapp or site?
Furthermore, such an approach could hardly by considered as RPM-
friendly.
I use only one tomcat instance on each physical server, and each
tomcat instance is hosting the same webapps/sites. On one machine
there is an Apache 2 + mod_jk installed, that collects the workers of
the different tomcat instances and does some load balancing. Whereas
a real cluster solution seems not to be possible with Cocoon, because
of some issues concerning the compulsive serialization of all session
data for replication, I use ajp13 workers, configured for with sticky
sessions. The new mod_proxy_ajp module did not work for me, so I use
mod_jk for this.
/L
Peter
Peter Flynn wrote:
I think the last time I asked, the recommendation was to make httpd
proxy Tomcat [...] Does anyone have any specific Dos or Donts about
this platform or configuration?
My personal experience with Tomcat for use with Cocoon 2.1 has been
terrible, both on RHEL and Debian.
We ended up using the (quite old) version of Jetty provided with
Cocoon
itself, along with the cocoon.sh wrapper script and Apache reverse
proxy
functionality, and it's been working like a charm ever since.
The only gotcha has to do with the AJP13 protocol, see here:
http://marc.info/?l=xml-cocoon-users&m=119201336509954
We haven't switched to Cocoon 2.2 yet, so I can't say much about it.
Tobia
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
