Denis Signoretto Il y a 6 années Hi David, really useful post. Thanks for sharing! Veuillez vous identifier pour voter. Répondre en tant que ... Annuler
(Vous) Il y a 6 années [...] Jorge Díaz: About HikariCP it is only used in case of configuring Liferay JDBC settings in your portal.properties I have a blog post up showing how you can use Hikari for your tomcat JNDI... [...] Read More Veuillez vous identifier pour voter. Répondre en tant que ... Annuler
Adrian Rodriguez Monedero Il y a 4 années - Edité Hi Dave, thanks for the post! > Liferay 7 CE and Liferay DXP default to using Hikari CP At which level is this default? I see that there is a hikaricp.jar in ROOT/WEB-INF/lib. Is this used for all the DB-connections? My concern is that if I configure a JNDI-DataSource, Liferay would put a connection pool on top of another connection pool. Perhaps HikariCP is used whenever a JNDI-DataSource is not used. This would make sense... Also, because there is already a hikaricp.jar and a slf4j.jar in ROOT/WEB-INF/lib, I was wondering if this would not cause any classloading problems if I put these files in lib/ext Greetings! Veuillez vous identifier pour voter. Répondre en tant que ... Annuler David H Nebinger Adrian Rodriguez Monedero Il y a 3 années - Edité Hi Adrian, sorry for the late reply... In lib/ext, this jar will be global and will trump a version deployed in a web app, but all it is doing is providing the classes, not the pool. When you follow this blog to define your connection pool in the application layer, when you use the jndi lookup that will return a datasource, but you shouldn't need to pool that, you just use it. The fact that it is pooled is encapsulated out of your way. Veuillez vous identifier pour voter. Répondre en tant que ... Annuler
David H Nebinger Adrian Rodriguez Monedero Il y a 3 années - Edité Hi Adrian, sorry for the late reply... In lib/ext, this jar will be global and will trump a version deployed in a web app, but all it is doing is providing the classes, not the pool. When you follow this blog to define your connection pool in the application layer, when you use the jndi lookup that will return a datasource, but you shouldn't need to pool that, you just use it. The fact that it is pooled is encapsulated out of your way. Veuillez vous identifier pour voter. Répondre en tant que ... Annuler