referring to this config guide for EAP 4.3:
how critical is entity caching for EJB 3 entity classes? i have set up a 2 node horz cluster that supports load-balancing, failover, and sticky sessions.
I have added the tag to web.xml as well as @Clustered to all SFSB's in my Seam app (in this case it's the Seam booking app).
It seems that the entity caching is related to the Hibernate 2nd level cache which is recommended for read-only or read-mostly tables.
In a small "normal" CRUD Seam app, is entity caching according to the config guide critical???
What are the disadvantages or consequences of not using entity caching? is it mainly performance?
And when a node does fail, is it true that the session and entity sync happens at that time (as well as at the end of session bean methods) such that when the session continues on the different node, everything is already sync'd up?
according to EJB 3 in action, the syncing happens at any of the following times (depends on app server implementation of syncing/caching):
1) end of EJB transaction
2) end of EJB method
3) when EJB container shuts down (node fails)
so of these 3 possibilities, what does JBoss do?