Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

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.

Change History (1)

comment:1 Changed 15 years ago by jmoore

  • Description modified (diff)
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.64105 sec.)

We're Hiring!