Derek Hohls wrote:
> In the meantime, rather than hacking around with all sorts of
> combinations, we are trying to locate and use another server
> (running Linux, which seems not to have these sorts of problems)
The server I was having that problem on was running Linux, so I believe
the issue to be OS-independent, but rather caused by some combination of
versions. Or maybe something else entirely which I have forgotten about!
> Do you know of any detailed comparison of Tomcat vs Jetty, especially
> for configuring and running under Apache?
Sure!
Jetty is much lighter on memory and starts / restarts faster. That's
all that matters to us, especially in development. Which means we are
using it in deployment too, to avoid potential problems.
To connect Apache and Tomcat one usually uses the AJP13 protocol, with
the AJP13 connector, which is supposed to be slightly faster than HTTP.
Unfortunately using Jetty 4.2.23's AJP13 port caused weird problems
(random NullPointerException when using continuations!) so we switched
to Apache's reverse proxy functionality. The configuration is like this:
<VirtualHost *:80>
ServerName www.yourwebsite.com
UseCanonicalName Off
ProxyPreserveHost On
ProxyPassReverse / http://10.0.0.3:8888/
ProxyPass / http://10.0.0.3:8888/
...
</VirtualHost>
In this example 10.0.0.3 is the Cocoon server. It could be 127.0.0.1.
Note #1: if the various Proxy* directives don't give you enough of a
fine-grained control over which requests go to Cocoon and which ones
stay in Apache, you can use rewrite rules with the [P] flag.
Note #2: when using reverse proxy, you won't find the remote IP address
(that of the web browser) in request.getRemoteAddr(), but rather in
request.getHeader('X-Forwarded-For')
HTH
Tobia
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
