RE: [JBoss-user] cache invalidation framework

[Sacha L. <sac...@ml...>]

Raghu,

This is all (and only) about cache, not distributed locking or
sychronisation => you won't get an exception or any problem except if you
setup your DB to exhibit such behaviour (optimistic locking at the db level
for example).

Cheers,


sacha

> -----Original Message-----
> From: jbo...@li... 
> [mailto:jbo...@li...] On Behalf Of raghuram
> Sent: vendredi, 11. avril 2003 08:14
> To: Jboss-User
> Subject: [JBoss-user] cache invalidation framework
> 
> 
> Hi,
> I'm new to clustering on JBoss and wanted to clarify if the Cache
> Invalidation Framework satisfies my requirements.
> I wanted to know what happens in the following scenario if 
> i've used the
> Cache Invalidation Framework with Commit Option A:
> Transaction 1 is started on Node 1 involving an update to  
> Entity Bean A.
> Transaction 2 is started on Node 2 involving an update to 
> Entity Bean A.
> Transaction 1 updates Entity Bean A and commits.
> At this point, I presume the cache on Node 2 should get invalidated.
> Will that happen, and if it does, will there be an exception thrown ?
> Thanks
> Raghu
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of 
> TotalView, The debugger 
> for complex code. Debugging C/C++ programs can leave you 
> feeling lost and 
> disoriented. TotalView can help you find your way. Available 
> on major UNIX 
> and Linux platforms. Try it free. www.etnus.com
> _______________________________________________
> JBoss-user mailing list
> JBo...@li...
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>