RE: clustering resin servers

Hi,

I now trying to configure resin act as web tier, with two instances of
engine servlet/jsp.
I have a ldap server for the web authentication (users than exists in the
ldap, can use the application, and the others not), but in the resin web
tier don't know howto configure this.
In the documentation page:
http://www.caucho.com/resin-3.0/security/authentication.xtp talks over
JdbcAuthenticator, but this is when the users are in a data base, not in
ldap.
With apache is very easy using the tag Location and module authnz.
Howto implement this with resin web tier?

Thanks
Cesar Jorge

-----Mensaje original-----
De: [email protected] [mailto:[email protected]]
En nombre de Scott Ferguson
Enviado el: jueves, 29 de junio de 2006 1:58
Para: [email protected]
Asunto: Re: clustering resin servers


On Jun 28, 2006, at 12:22 PM, Eric Kreiser wrote:

> I have a cluster defined with 2 srun's... 1 as a primary and 1 as a  
> backup... my issue is that when my primary goes down... the next  
> request fails while the second request correctly goes to the backup  
> srun.  Why isn't the first request correctly sent to the backup?

Well, this is a reason we'll start encouraging people to use Resin as  
the web tier.  (Plus we're improving the load balancing in 3.0.20).

The issue is that the web-tier doesn't know that the backend has  
failed until it gets a failure from the write() call.

A reasonably-sophisticated load balancer (like the Resin one) can  
retry the same request on a second backend.   mod_caucho can't.  (And  
we will not be adding that capability to mod_caucho because it's not  
as testable as Resin is.)

Actually, there are a number of advantages of using Resin in the web  
tier.

   * Resin can already act as a proxy cache, so static or pseudo- 
static files can be served directly from cache.

   * Because Resin is fully threaded, it can share information and  
sockets and caches more easily than Java can.

   * Resin's load balancer can do some clever things like warmups (in  
3.0.20) and more effectively dealing with updates (probably 3.0.21).

-- Scott

>
> I front end resin with apache 2.0.55.
> Running resin 3.0.14
>
>
>