| Random deadlock/hang during commit in EJB3 application [message #491656] |
Thu, 15 October 2009 12:11  |
 Torben Putkonen
Messages: 34
Registered: July 2009 |
Member |
|
|
I'm not sure this issue is caused by EclipeLink, but I really appreciate insight into what could be causing this behaviour.
We are experiencing random deadlocks in our EJB3 application. Sometimes one MDB, when using several threads, locks randomly in transaction commit.
Log contains the following lines before hanging:
UnitOfWork(12587905)--Thread(Thread[RMICallHandler-43,5,HTTP ThreadGroup])--TX beforeCompletion callback, status=STATUS_ACTIVE
UnitOfWork(12587905)--Thread(Thread[RMICallHandler-43,5,HTTP ThreadGroup])--begin unit of work commit
UnitOfWork(12587905)--Thread(Thread[RMICallHandler-43,5,HTTP ThreadGroup])--TX afterCompletion callback, status=COMMITTED
In a normal situation, there would also exist information about end of UnitOfWork.
First we replaced CMT with BMT, but it didn't help. Next the commit was surrounded with a synchronized() call, and this seems to have fixed the issue.
We have encountered this issue with both EclipseLink and TopLink Essentials, and with Oracle database 10G and 11G. Oracle AS is 10G.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03557 seconds
] 
Search
Help
Register
Login
Home
