I have an entity bean (A) that represents a small number of business objects which are used by a large number of other entities (B). We are never actually changing the data in A, only reading it.
Because we are not chaning the data there is no reason why two threads/transactions shouldn't be able to read data from the entity at the same time. However, we seem to be getting threads going into a wait-state accessing A, the log shows millions of lines of: [OperatorAccountEJB] LOCKING-WAITING (TRANSACTION) for id MGX001ctx.hash 3310756 tx:TransactionImpl:XidImpl [FormatId=257, GlobalId=svr-mgx-ssa-j2e1.gw1.magex.com//53, BranchQual=] Can the behaviour be modified such that other threads can concurrently read the entity? Or is an entity bean fundamentally unsuitable for an object with this type of access pattern? Rich. [JBoss-2.2.2, Sun jdk1.3.01, Linux/Solaris] ============================================================================== This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. All information is the view of the individual and not necessarily the company. If you are not the intended recipient you are hereby notified that any dissemination, distribution, or copying of this communication and its attachments is strictly prohibited. If you have received this email in error please notify: [EMAIL PROTECTED] ============================================================================== =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
