Thanks All.   I'm quite happy with mod_proxy, I just wanted to make sure I wasn't missing the boat on mod_wl.

It seems as if mod_wl has some advanced features if you were using clustering, etc on the back end.

~Todd

On Mon, Feb 9, 2015 at 9:01 AM, Jim Jagielski <jim@jagunet.com> wrote:
You could always try mod_proxy_ajp, which uses the mod_proxy framework,
but communicates via AJP. It's better at detection of silently
dropped AJP connections.

> On Feb 9, 2015, at 3:18 AM, Dr James Smith <js5@sanger.ac.uk> wrote:
>
>
> We used mod_jk for ages and have recently flipped back to mod_proxy for our java/tomcat apps, we found that we had connectivity issues with mod_jk - if the connection between apache/tomcat is severed then mod_jk did not always work cleanly - and subsequent requests would just hang. mod_proxy didn't have the problem.
>
> The problem showed it self when we started segregating machines into virtual firewall zones - so traffic between machines was controlled.
>
> It does mean that we don't have as easy a load-balanced setup  - although we do send the requests back through our front-end load balancers and this seems effective.
>
> James
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> http://www.avast.com
>
>
>
> --
> The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org