Hi Dan,
<vendor>
Take a look at the following address for how Inprise in
Inprise Application Server 4 implements what you need :
http://www.borland.com/devsupport/appserver/faq/Availability_Scalability_Performance.html
This is from the document there :
Failover is supported by leveraging the Naming Service and the osagent. We support
failover of all types of EJBs. To summarize the behavior:
2) Entity Beans. From the Container standpoint, Entity Beans are similar to Stateless
Session Beans, except that before being able to use a replica entity, it needs to be
loaded in. The current transaction will fail, as it should. Both the resource and the
synchronization objects associated with the original (failed) entity in VM 1 will be
unavailable, and the transaction manager, presuming rollback (as per the OTS/JTS
specification) will roll back the current transaction. However, subsequent
transactions will simply fail-over to use the replica entity in VM 2, and will
continue correctly.
</vendor>
eyal.
===========================================================================
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".
