Hi all,

I know how to cluster Orion..after all, its pretty easy. What I want to know
from someone who knows..is if in the 1.5.2 version all the bugs (if there
were actually any) are worked out. Does Orion cluster with no problems? Does
session fail-over and application context fail-over work without a hitch
(providing all objects in the session and/or context are serializable)? If
you have two machines in an island, and the session begins on one..does it
automatically "copy" any session info to the other box for you? If you shut
that box off, and all requests go to the 2nd box, does the session still
exist with all objects still in memory?

I take it each and every request on a clustered box requires the session to
be duplicated exactly as is to the other machine? If this is the case, at
what "rate" does Orion copy out the session and anything else to another
server in the island (or to each and every server in the island)? How does
this affect performance as compared to using just a single box without
clustering..is it 2 to 3 times slower because of not only copying its
session to one or more boxes, but also having to deal with "merging" other
boxes context/session information into its own? Or does a cluster simply
create the objects and session stuff on each box as its generated (thus..its
not some background thread that copies session info when it has time to
other boxes)?

Is it equally good at clustering on the EJB tier (so scalability on the EJB
tier or the front-end WEB tier is equally as easy)?


Thanks.

Reply via email to