Ok thanks Brian.
My instinct is to go with the default configuration - UDP. And I also
understand from your comments why this configuration will be the best for most
cases.
The reason I ask is that about 3 years ago (before my time) it was reported
that with our app (then using I think JBOSS 2
Hi - we have started trying to understand the best (most reliable, most
performant) networking configuration for clustering with JBOSS AS..
It appears (from the standard, shipped service xml) that JBOSS recommends UDP
multicast as the best way to support session replication and distributed
cach
Hi - these question relate to establishing the safe operation of buddy
replication under AS 4.0.5.
Selection of Buddies
Say we have nodes a1, a2 and a3 and they are booted in that order. What we see
is that when a2 starts it forms a buddy pair with a1. Then when a3 starts a1
becomes the backup
Thanks Brian - these settings seem to have made a significant improvement. We
have also started trimming down on the amount of session state and that is also
a big win for replication.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148698#4148698
Reply to th
Sorry - re-posting with code tags..
PROBLEM
We are trying to use session replication with ASS 4.0.5 but running into
significant performance problems.
Specifically, under load We are seeing a 3-4x cpu increase in cpu on the app
servers as a result of them
trying to do session replication.
Unfo
PROBLEM
We are trying to use session replication with ASS 4.0.5 but running into
significant performance problems. Specifically, under load we are seeing a 3-4x
cpu increase in cpu on the app servers as a result of them trying to do session
replication.
Unfortunately the application is pretty
Brian - ok, thanks for the input
I will try running the new jgroups and jboss-cache still using AS 4.0.5. So you
are saying these will still be compatible - right? Is there a matrix somewhere
that defines which version of which components can go together. e.g. what
versions of jgroups or jboss-
BTW - I assume there is no reason (and one should not) configure an eviction
policy into the tc5-cluster.sar/jboss-service.xml.
This understanding is based on your comment
anonymous wrote : the effect of a logout, if you call session.invalidate() the
session is removed cluster-wide. (If you ju
Brian - thanks for your input..
Re memory: I researched further and think this is the reason.. We have 3 app
servers. The start sequence is a1, a2, a3. When a2 starts a1 (already started)
and a2 form a buddy pair (they appear to both backup each other). Then when a3
starts it looks like a2 also
Hi - we have a test cluster with three nodes a1, a2, a3. We have configured
Tomcat sessions replication with buddyreplication.NextMemberBuddyLocator and
one buddy per node.
Buddy Replication Question
I assume that with this setup we would have something like a2 replicates a1's
sessions, a3 r
10 matches
Mail list logo