User Story #1158 (new)
Opened 15 years ago
Last modified 15 years ago
Find optimal JTA implementation — at Version 1
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | critical | Milestone: | OMERO-Beta4 |
Component: | ORM | Keywords: | jta, orm, database, transactions |
Cc: | Story Points: | n.a. | |
Sprint: | n.a. | Importance: | n.a. |
Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description (last modified by jmoore)
While using c3p0 in blitz, it was found that large sections of code were unprotected by transactions. Since then, we've been testing various JTA providers to improve the situation.
JOTM
Under high-load could become completely dead-locked.
atomikos
After 2-3 weeks of uptime, the server fails with "heurtistic" exceptions.
Bitronix (btm)
With 2PC, hangs on one of the first server calls; with 1PC throws "can only enlist one Lru source"
JBossTS / Arjuna
Without conncetion reconnect, consumes all Postgres connections; with, throws heuristic exceptions.
Apparently our use of transactions is not compatible with any JTA implementation (or the spec??) and so some re-architecting is necessary.