0 Replies Latest reply on Oct 6, 2004 10:41 AM by Robert Costanzo

    Entity EJB Locking Policies for JBoss 3.2.5

    Robert Costanzo Newbie

      I am currently using JBoss 3.2.5. When we first went into production, it was on 3.2.1. Does anybody know if the locking policies have progressed since then? We are using the default policy, which causes some object lock contention at the entity EJB level. An InstancePerTransaction policy would work wonderfully with our application, but as of 3.2.1, you could not use caching commit option 'A' with it (which is unacceptable performance-wise for our app). Also, any of the other locking policies really weren't up to snuff in 3.2.1 for production use.

      So...if anybody is using a better locking policy than the default queued pessimistic one, please let me know. Or know if/when a 'NoLock' policy will be able to be used with a commit option 'A' for caching.

      Thanks!