Atomikos vs JOTM vs Bitronix vs? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 9 years ago.

Improve this question

I am new to JTA and it's underlying transaction managers. Can anyone explain the pros/cons of 开发者_StackOverflow社区each of these? Feel free to add others I didn't list in title.

Also, don't the major applications servers (WebSphere, JBoss, Glassfish) have their own JTA compliant transaction manager? In those environments, would you still use these third party implementations?

---

I am new to JTA and it's underlying transaction managers. Can anyone explain the pros/cons of each of these? Feel free to add others I didn't list in title.

Standalone transaction managers I'm aware of include Bitronix, SimpleJTA, Tyrex (dead?), JOTM (used in Jonas), GeronimoTM/Jencks (used in Geronimo), JBossTS (used in JBoss) and Atomikos.

I've never tested them all extensively (and this is what you would have to do if you have to choose one) so I can't provide an exhaustive pros/cons (and that would require some work). But here are some links:

• Transaction Manager for Stand-Alone Java Applications (cover some of them with pros/cons)
• O(pen) S(ource) JTA Transaction Managers
• Re: [xmlblaster-devel] JTA compliance

Just in case, here is my very personal point of view:

• I've seen lots of complains about JOTM.
• I think that GeronimoTM/Jencks lacks of documentation.
• SimpleJTA doesn't implement JTS and is not active.
• Bitronix is decently documentation but doesn't offer support.
• Atomikos is an impressive product, well documented and does offer support.
• JBossTS aka ArjunaTS is definitely a mature product (see the announcement of the acquisition for some history) and does offer support.

Personally, I'd shortlist Atomikos and JBossTS and test them hardcore if I had to choose one.

Also, don't the major applications servers (WebSphere, JBoss, Glassfish) have their own JTA compliant transaction manager?

Of course they do, JTA is part of the Java EE specification, a Java EE server has to support it.

In those environments, would you still use these third party implementations?

No, I'd use the provided transaction manager (for simplicity, support, etc).

---

I have tested Atomikos and JOTM with Jetty. Atomikos worked fine and I fully recommend it. I made e.g. automated unit tests for testing distributed transactions in my application and these tests worked fine.

As far as JOTM is concerned I am quite sure that it fakes the 2-phase commit protocol at least sometimes. I had a PostgreSQL database with the 2-phase commit capabilities turned off and JOTM was able to work as if I had real distributed transactions. Real transaction managers (e.g. the one implemented in GlassFish) reported an error in such a case.

I used JPA2 with Hibernate 4 in my application if it matters.