Hi Matthew,
pax-jdbc-pool-dbcp2 as well as pax-jdbc-pool-aries should both be able
to provide XA enlisting poolable DataSources.
Aries JPA and Transaction actually use the above in their integration
tests. So they should work together nicely.
I got two tutorials that both use XA transactions
Thanks very much for the references, I will definitely be looking over them.
I was hoping the dbcp2 bundle would allow for the same XA capability, as I
would prefer dbcp2 pooling since it seems fairly analogous to my current
pooling - bonecp. However, I did some testing with dbcp2 and got exceptio
[1] is a snippet from the stacktrace I get when using pax-jdbc-pool-dbcp2
instead of -aries. As you can see,
ManagedJDBCConnection#localTransactionStart appears to call setAutoCommit on
the connection class, which the DBCP2 impl short circuits at [2].
This same exact environment seems to run fine
Honestly I have no idea why tranql sets the autocommit. I would not
expect that it needs to be tweaked.
I can imagine that dbcp2 does not allow to change autocommit for XA
transactions as the commit should
only be done when the XA transaction commits. Not sure about this either
though.
I pro
Ok, thanks so much for the suggestions.
It is interesting to me that this isn't something someone else has seen
since I feel like I am using the pax-jdbc and aries bundles in a
straightforward way.
Do you have a recommendation of using the aries pool bundle vs. the dbcp2
one? I'm not set on eithe
Not sure why you hit the problem with dbcp2 and eclipselink. I have some
itests running
with eclipselink and they showed no problems. Will look into what
versions I used exactly.
I am not very familiar with the aries pooling but it should work fine.
Christian
Am 23.09.2015 um 02:48 schrieb ma
