Hello,

I am experiencing a problem where pax-jdbc-config (version 1.3.0) is creating 
duplicate Derby Data Sources.  I copy the data source configuration file to  
Karaf's etc/ directory, after a while I can see it created two identical Data 
Sources.

The configuration file: org.ops4j.datasource-querier.cfg

osgi.jdbc.driver.name = derby
dataSourceName=querier
url=jdbc:derby:derby-data/querier;create=true

user=enquery
password=XXXX
databaseName=querier

ops4j.preHook=querierDB

It creates duplicate Data Sources:

karaf@root()> service:list DataSource                                           
                                                                                
                                                           
[javax.sql.DataSource]
----------------------
 databaseName = querier
 dataSourceName = querier
 felix.fileinstall.filename = 
file:/Users/asoto/test/etc/org.ops4j.datasource-querier.cfg
 ops4j.preHook = querierDB
 osgi.jdbc.driver.name = derby
 osgi.jndi.service.name = querier
 password = enquery
 pax.jdbc.managed = true
 service.bundleid = 169
 service.factoryPid = org.ops4j.datasource
 service.id = 238
 service.pid = org.ops4j.datasource.b161e768-e5f8-40bb-b19f-40cab9111316
 service.scope = singleton
 url = jdbc:derby:derby-data/querier;create=true
 user = enquery
Provided by : 
 OPS4J Pax JDBC Config (169)
Used by: 
 JPA (22)
[javax.sql.DataSource]
----------------------
 databaseName = querier
 dataSourceName = querier
 felix.fileinstall.filename = 
file:/Users/asoto/test/etc/org.ops4j.datasource-querier.cfg
 ops4j.preHook = querierDB
 osgi.jdbc.driver.name = derby
 osgi.jndi.service.name = querier
 password = enquery
 pax.jdbc.managed = true
 service.bundleid = 169
 service.factoryPid = org.ops4j.datasource
 service.id = 282
 service.pid = org.ops4j.datasource.b161e768-e5f8-40bb-b19f-40cab9111316
 service.scope = singleton
 url = jdbc:derby:derby-data/querier;create=true
 user = enquery
Provided by : 
 OPS4J Pax JDBC Config (169)

Also:

karaf@root()> jdbc:ds-list
Name    │ Product      │ Version               │ URL                           
│ Status
────────┼──────────────┼───────────────────────┼───────────────────────────────┼───────
querier │ Apache Derby │ 10.13.1.1 - (1765088) │ jdbc:derby:derby-data/querier 
│ OK
querier │ Apache Derby │ 10.13.1.1 - (1765088) │ jdbc:derby:derby-data/querier 
│ OK


I think it must be specific to Derby, as the same works fine if the driver is 
MariaDB.
Any clues?

Best regards,
Alex soto




Reply via email to