RE: PAX JDBC 1.0.1 pools

:18 AM To: user@karaf.apache.org Subject: Re: PAX JDBC 1.0.1 pools Hi Scott, sorry for the late response. Took a while until I found time to look into the hikari pool code. You need to prefix the hikari properties with "hikari.". All these properties will be stripped of the prefix

Re: PAX JDBC 1.0.1 pools

Schneider *Sent:* Friday, February 24, 2017 11:30 AM *To:* user@karaf.apache.org *Subject:* Re: PAX JDBC 1.0.1 pools See https://ops4j1.jira.com/wiki/display/PAXJDBC/Pooling+and+XA+support+in+1.0.0 For H2 and hikari you could use: osgi.jdbc.driver.name=H2 pool=hikari databaseName=test user=s

RE: PAX JDBC 1.0.1 pools

Hadn’t really thought of the versioning issue. Like I said, not an issue I have at the moment. Thx. From: Timothy Ward [mailto:tim.w...@paremus.com] Sent: Friday, March 03, 2017 11:39 AM To: user@karaf.apache.org Subject: Re: PAX JDBC 1.0.1 pools Hi Scott, I’m curious as to why you can’t just

Re: PAX JDBC 1.0.1 pools

h offhand I don’t see the use case > although I suspect that’s just because it hasn’t affected me yet. > > As always, thanks for your help. > > Scott > > From: Timothy Ward [mailto:tim.w...@paremus.com] > Sent: Friday, March 03, 2017 10:50 AM > To: user@karaf.apache

RE: PAX JDBC 1.0.1 pools

offhand I don’t see the use case although I suspect that’s just because it hasn’t affected me yet. As always, thanks for your help. Scott From: Timothy Ward [mailto:tim.w...@paremus.com] Sent: Friday, March 03, 2017 10:50 AM To: user@karaf.apache.org Subject: Re: PAX JDBC 1.0.1 pools Hi Scott, Well

Re: PAX JDBC 1.0.1 pools

aults to 10,800,000 (3 hours). The > maximum time in milliseconds that a connection may remain open before being > closed. > > Scott > > From: Timothy Ward [mailto:tim.w...@paremus.com] > Sent: Wednesday, March 01, 2017 9:50 AM > To: user@karaf.apache.org > Subject: Re:

RE: PAX JDBC 1.0.1 pools

closed. Scott From: Timothy Ward [mailto:tim.w...@paremus.com] Sent: Wednesday, March 01, 2017 9:50 AM To: user@karaf.apache.org Subject: Re: PAX JDBC 1.0.1 pools Actually, the JDBC providers in Apache Aries Transaction Control do use HikariCP for their connection pooling support, it’s just abstracted

Re: PAX JDBC 1.0.1 pools

I will take a look at Transaction Control, but my first scan shows it is implementing its own connection pool? I wish to continue to use HikariCP as my pool, thus the source of my question. But let me give a little more background. I presently use Blueprint to define datasource XML files that

Re: PAX JDBC 1.0.1 pools

Transaction Control can already be used with a DataSource, Driver, DataSourceFactory, you name it. It also doesn’t have special configuration, it’s config admin just like everything else. The scoped connection is also not special, and can be passed to all manner of other libraries. You can

Re: PAX JDBC 1.0.1 pools

It would be nice if the transaction control service would also support DataSources as services. So would would only need to teach people one variante to configure them. Transaction control is special in its config and it can not be reused for other usages of a database. Christian 2017-03-01

RE: PAX JDBC 1.0.1 pools

I too am trying out the HikariCP pooling and haven't figured out how to change/specify pool settings. I have a .cfg file that creates a pooled data source just fine, with TRACE logging on I see HikariCP initializing and all the default settings. And the pool is used as I use the data source.

RE: PAX JDBC 1.0.1 pools

: Friday, February 24, 2017 11:30 AM To: user@karaf.apache.org Subject: Re: PAX JDBC 1.0.1 pools See https://ops4j1.jira.com/wiki/display/PAXJDBC/Pooling+and+XA+support+in+1.0.0 For H2 and hikari you could use: osgi.jdbc.driver.name=H2 pool=hikari databaseName=test user=sa password= dataSourceName

Re: PAX JDBC 1.0.1 pools

See https://ops4j1.jira.com/wiki/display/PAXJDBC/Pooling+and+XA+support+in+1.0.0 For H2 and hikari you could use: osgi.jdbc.driver.name=H2 pool=hikari databaseName=test user=sa password= dataSourceName=test2 To install in karaf: feature:repo-add pax-jdbc 1.0.1 feature:install pax-jdbc-config

Re: PAX JDBC 1.0.1 pools

Hi Scott, The OSGi Transaction Control service has built in support for connection pooling. There's an en route example here: https://github.com/osgi/osgi.enroute.examples.jdbc Regards, Tim Sent from my iPhone > On 24 Feb 2017, at 16:12, Leschke, Scott wrote: > > I’m