Which version of JBoss are you using?
I'am using JBoss 3.2.3 ...
I am no expert in this area, but I've experienced a similar problem with our application.
I have been using JBoss 2.4.3 and not 3.2.3 so my comments may not be applicable but I too have experienced a similar problem where JBoss has not thrown an ApplicationDeadlockException in a situation where I would have expected it to do so.
You will need to review your use of your entity beans and determine if the default combination of pessimistic locking coupled with commit option A is appropriate for your use case. It would be also worth considering the use of read-only methods in your beans (something not available to me in v2.4.3).
Can you please provide some more inputs on - determining the suitability of the 'default combination of pessimistic EJB locking & commit option A' for the use-case. An example for analysing would be very helpful for me.
1. the default commit option is 'B' & not 'A' - right ??
2. Read-only methods cannot be used in my case - since, timeout is happening only when i try to reads a modifiable field.[which cannot be made read-only, as concurrent writes are also possible]
Thanks in advance !!