I have a question on the maintaining of state consistency and
scalability on ejb servers.
If I have, say, two ejb servers working in a load-balanced arrangements.
Both servers are serving the same ejb classes.
Client A is editing the Customer entity bean relating to "John Smith" on
server A.
The Customer entity bean relating to "John Smith" is also cached in
memory on server B after a previous update. (I am assuming ejb servers
cache objects in memory)
Client A commits his changes to the underlying database.
How does ejb ensure that the in memory cached instance of "John Smith"
on server B is updated to reflect the changes made by Client A?
Does it fire off an "update" event to all the servers?
If so, and we have n servers then I image we have a scalability problem
of order n-1. (Ie the server has to notify every other server that the
update has happened)/
If it doesn't then how can I possibly use entity beans in a load
balanced environment?
TIA
--
Tim Fox (��o)
Hyperlink interactive
http://hyperlink.com
email: [EMAIL PROTECTED]
phone: +44 (0) 207 240 8121
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
