Clustering and Commit Option A

[markr]

Neither Jboss (currently) nor Weblogic Server support clustered commit-option-A entity beans. Commit-option-A beans can give a huge performance benefit by reducing the number of round-trips to the database. Not being able to use them in a cluster will negate the performance gains made by clustering. It seems that clustering JBoss will push the performance bottleneck out of the application server onto the database.

Does anyone have any ideas of ways to get around this? Patterns (i.e., the Seppuku Pattern), Third Party Products?

Mark

[seven]

IMHO I don't think the seppuku pattern (http://www.theserverside.com/patterns/thread.jsp?thread_id=11280) ensures integrity over the cluster because as long as ACID properties are not met over the cluster cache. It can be used really for EJB's that contain non critical information (and the stock example is unfortunate).

But we can try to look over some cache solutions that I've heard (but not even try them)

http://www.persistence.com/products/edgextend/index.php
http://www.exceloncorp.com/
http://www.gemstone.com/products/jboss/download.php
http://www.tangosol.com/download.jsp
http://www.versant.com/products/download/index.cfm

Hope this helps.