We are making a migration of our application to version 4.2.0 We have verified that in the previous version (karaf 4.0.7) multiple connections were made to the database when starting the web application:
postgres=# select datid, datname, usename, application_name, client_addr from pg_stat_activity where datname='ajal_db'; datid | datname | usename | application_name | client_addr -------+---------+---------+------------------+---------------- 16395 | ajal_db | ajal | | 172.24.208.100 16395 | ajal_db | ajal | | 172.24.208.100 16395 | ajal_db | ajal | | 172.24.208.100 16395 | ajal_db | ajal | | 172.24.208.100 16395 | ajal_db | ajal | | 172.24.208.100 16395 | ajal_db | ajal | | 172.24.208.100 16395 | ajal_db | ajal | | 172.24.208.100 (7 rows) In the new application (karaf 4.2.0): postgres=# select datid, datname, usename, application_name, client_addr from pg_stat_activity where datname='ajal_db'; datid | datname | usename | application_name | client_addr -------+---------+---------+------------------+---------------- We also check that the application is slower. Using H2 we can see that the lock.db file is created and destroyed after each query.This did not happen in version 4.0.7, where the file is always created. The datasource configFile: #Postgres url = jdbc:postgresql://172.24.208.100:5432/cecom osgi.jdbc.driver.name = PostgreSQL JDBC Driver user = ajal password = pool=dbcp2 -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
