Greetings, I'm doing an access authorization with an entity bean which has field of maximum connections available which should be updated. So I must have synchronized access to my entity bean.
Initially I had my entity bean with "Clustered CMP 2.x EntityBean" configuration, but when I changed to "Standard CMP 2.x EntityBean with cache invalidation", I gain a major improvement about 50% due of the disappearing of the *load operation* since the commit option passed from B to A. I would like to ask you what is the feature of clustered configuration against the standard configurations? Please be aware that I will use my application servers in cluster! Could the *nonexistence* of load operation bring me some incoherence problems even if I never update my database without an invalidation cache after? My unknown problem is what happens to the different jboss instances that would receive a request updating the same entity bean instance? Will the cluster handle the coherence of data? thanks. regards, Pedro Salazar -- -PS ------------------------------------------------------- This SF.net email is sponsored by OSDN's Audience Survey. Help shape OSDN's sites and tell us what you think. Take this five minute survey and you could win a $250 Gift Certificate. http://www.wrgsurveys.com/2003/osdntech03.php?site=8 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
