I had to refactor my question :-)
Current situation:
- war application with eg WebService (soap) deployed on Weblogic
- there is class with Spring @Configuration defined with @Bean method which returns Datasource inside (no HikariCP or other distributions)
- @Webservice is synchronized, so 2nd request will wait for the 1st call
- db connection is established via jndi with weblogic
- Weblogic has eg 15 connections available
- there is only 1 client application (war)
Jndi declaration placed inside application.properties provides itself connection pool defined inside Weblogic, so what potential benefits would be from using in this situation (Weblogic with own setting related to connection pool) HikariCP ?
Can I treat this like second layer ? so there would be:
- weblogic connection pool as a server layer
- hikari connection pool as a internal application layer
Where eg Hikari would provide eg different settings even if in Weblogic is 15 available connections in a pool (Hikari could limit it to eg 10 via own settings ?).
regards E.