RE: [JBoss-user] jBoss 3.0 clustering question...

[Jim A. <ji...@ar...>]

--On Saturday, November 24, 2001 9:07 AM +0100 Sacha Labourey 
<Sac...@co...> wrote:

> All nodes for the same beans will use the same database: we use
> pessimistic locking at the database level (i.e. the "select ... for
> update" trick) If you want other locking scheme, you can use MVCSoft
> persistent manager (you can buy it from JBoss web site, it doesn't cost
> much and seems to be very nice): it offers different locking mechanism at
> the database level AND application server level.

Ah, I see. So each of the two jBoss installations should be configured to 
use the very same database? And any database replication should be 
completely separate from jBoss. OK, I see.

>> We would like to cluster across data centers (one in Providence and the
>> other in Hartford, for example). Can this be done?
>
> In this case, I think you should better look at database clustering tools.
> And I don't know if JBoss clustering is what you want: if Providence
> server fails, do you really want your client application to contact your
> server at Hartford? (I mean from a WAN bandwidth perspective?) If yes,
> then go ;)

We were wondering what the bandwidth requirements between the jBoss servers 
would be. The clients are distributed about the globe anyhow.

>> Finally, is there anything we can do for servlet session clustering?
>
> We think about it, we think about it ;)

I have always felt that this is the best reason to use SFLBs ;-)

Thanks very much!



********************************************
I shall be telling this with a sigh
Somewhere ages and ages hence:
Two roads diverged in a wood, and I -
I took the one less traveled by,
And that has made all the difference.

- Robert Frost, 1916