Re: WebLogic9.1 Clustering with Spring

Nandkishore ** <> writes:

I think you are probably out of luck then. Most clustering tends to be
session oriented as that is how you get good scalability. You could
try using a distributed cache.

andy

> I don't think puttingthis beans in Session will work in my case.
> [b] 1)[/b]The first thing is the replication which I want is not for a
Client's Session. Whatever the changes takes place in an object should have to
be replicated across the overall cluster irrespective of a Client' HTTP Session
as the application is a request/response kind of paradigm(it doesn't create any
session, so can't use HttpClusterServlet with session replication). I mean to
say that as soon as it receives a request it just send back an OK response and
then interanally starts working(here it starts updating the singleton beans).
The problem is when another server receives the request it won't be having those
upadations which the first server has done.
>
> [b]2)[/b]Also as far the session replication is concerned whenever there is
change in the Session attribute object, weblogic cluster won't  replicate it
until and unless setAttribute is called again. I can't afford doing at the every
point becuase the objects are chainging frequently and anyways  this session
replication can't really help me because of the (1).
> Please let me know if you I got you right and I hope you must have
understood my problem now.So please let me know if still  what you are saying is