Re: Re: Pax-JDBC 1.1 hikari pool and XA Support

2017-07-11 Thread Guillaume Nodet
Try with pool.poolMinSize and pool.poolMaxSize ... Basically, prefix all the following properties with "pool." : https://github.com/apache/aries/blob/trunk/transaction/transaction-jdbc/src/main/java/org/apache/aries/transaction/jdbc/RecoverableDataSource.java#L50-L64 Guillaume 2017-07-11 10:02 G

Re: Re: Pax-JDBC 1.1 hikari pool and XA Support

2017-07-11 Thread sahlex
Thanks for the enlightenment. I totally overlooked that part of the hikari documentation. Using pool.name works perfectly! Besides, I didn't find a way to set other properties than the name, like MaxSize. Is it possible somehow (maybe I should open another topic)? Thanks, Alexander. -- View

Re: Re: Pax-JDBC 1.1 hikari pool and XA Support

2017-07-11 Thread Guillaume Nodet
The hikari doc says "Note XA data sources are not supported." on https://github.com/brettwooldridge/HikariCP ... I think you need to set the pool.name property in the config for the datasource to be wrapped. 2017-07-11 9:15 GMT+02:00 : > I thought I was using Aries Transaction Manager still? > D

Antw: Re: Pax-JDBC 1.1 hikari pool and XA Support

2017-07-11 Thread alexander.sahler
I thought I was using Aries Transaction Manager still? Does it mean, that hikari pooling does not support XA? When I use aries pooling, it complains about "Unable to recover XADataSource: aries.xa.name property not set". I tried to set it in the pax-jdbc datasource file but it doesn't seem to ma

Re: Pax-JDBC 1.1 hikari pool and XA Support

2017-07-10 Thread Tim Ward
Another option would be to look at Apache Aries Transaction control. That provides a simple, effective model for connection pooling, resource lifecycle management, and transaction enlistment. It will also be the reference implementation of the OSGi Transaction Control specification when OSGi R7

Re: Pax-JDBC 1.1 hikari pool and XA Support

2017-07-10 Thread Guillaume Nodet
I don't recommand using non XA specific pooling mechanism for JDBC support, unless you don't care about the ability to recover in-flight transactions (which doesn't play well with wanting XA). If you're using the geronimo/aries transaction manager, you may want to use the pax-jdbc-pool-aries instea