>From: Tim Fox [mailto:[EMAIL PROTECTED]]
>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?
EJB does not mandate clustering let alone synchronisation between components
arranged in a cluster.
>Does it fire off an "update" event to all the servers?
No. Not mandated by EJB.
>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?
You have the following options:
Go for Commit Option C and lose the benefit of bean instance caching
Select a vendor that does support option A with multiple JVMs
Combine Option A with your own database trigger driven update
Regards,
Hamid
===========================================================================
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".
