id summary reporter owner description type status priority milestone component resolution keywords cc rd_points sprint story_priority 1158 Find optimal JTA implementation jamoore jamoore "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. " story closed critical OMERO-Beta4 ORM fixed jta, orm, database, transactions