karaf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Nodet <gno...@apache.org>
Subject Re: Re: Pax-JDBC 1.1 hikari pool and XA Support
Date Tue, 11 Jul 2017 07:35:00 GMT
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 <alexander.sahler@brodos.de>:

> 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 make use of it.
>
> Alexander
>
>
> >>>
> 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 goes final.
>
> Tim
>
> Sent from my iPhone
>
> On 10 Jul 2017, at 16:18, Guillaume Nodet <gnodet@apache.org> wrote:
>
> 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 instead which will support recovery.
>
> Guillaume
>
> 2017-07-10 17:03 GMT+02:00 sahlex <alexander.sahler@brodos.de>:
>
>> Hello.
>>
>> When using pax-jdbc 1.1.0 (on karaf 4.0.8) to be able to use hikari pool
>> support everything is working fine until I switch on XA support.
>> In this case the DataSource is not created! When I comment out the XA
>> support from the datasource factory config file, the DataSource pops up
>> again.
>>
>> I have transaction service 2.1.0 deployed (tried with 1.1.1 as well):
>> list | grep Trans
>> 164 | Active | 80 | 2.1.0 | Apache Aries Transaction Blueprint
>> 165 | Active | 80 | 1.3.1 | Apache Aries Transaction Manager
>>
>> My configuration file:
>> osgi.jdbc.driver.name = mariadb
>> dataSourceName = whatever
>> databaseName = whatever
>> user = xxx
>> password = xxx
>> pool = hikari
>> # xa = true
>> hikari.maximumPoolSize = 200
>> hikari.connectionTimeout = 400
>> url = jdbc:mariadb:failover://1.2.3.4/bam?characterEncoding=UTF-8&
>> useServerPrepStmts=true
>>
>> service:list DataSource
>> [javax.sql.DataSource]
>> ----------------------
>> databaseName = whatever
>> dataSourceName = whatever
>> felix.fileinstall.filename = file:/opt/xxxxxxxxxxxxxxxxxxxxxxxx
>> hikari.connectionTimeout = 400
>> hikari.maximumPoolSize = 200
>> osgi.jdbc.driver.name = mariadb
>> osgi.jndi.service.name = whatever
>> password = xxx
>> service.bundleid = 126
>> service.factoryPid = org.ops4j.datasource
>> service.id = 391
>> service.pid = org.ops4j.datasource.f349f611-9c2e-48a7-8ac0-3789a8f5dd66
>> service.scope = singleton
>> url = jdbc:mariadb:failover://172.17.42.50:3309/whatever?character
>> Encoding=UTF-8&useServerPrepStmts=true
>> user = xxx
>> Provided by :
>> OPS4J Pax JDBC Config (126)
>>
>> Regards, Alexander
>>
>>
>>
>>
>>
>> --
>> View this message in context: http://karaf.922171.n3.nabble.
>> com/Pax-JDBC-1-1-hikari-pool-and-XA-Support-tp4050977.html
>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>
>
>
>
> --
> ------------------------
> Guillaume Nodet
>
>


-- 
------------------------
Guillaume Nodet

Mime
View raw message