JDBC Connection Pooling

[Lars Feistner]

Hi all,

I have multiple jdbc attributeRepositories that connect to the same DB. Thus I just found out that each attributeRepository is using its own Hikari ConnectionPool which makes sense if all would connect with different Databases. In my case this is overhead.

Can I configure cas in a way that all the attributeRepository are using the same Hikari ConnectionPool?

Best regards,
Lars

--

	Lars Feistner Entwicklungsleitung Phone: +49 6221/186749-5 Mail: l.fei...@cares.institute
	Institut für Kommunikations- und Prüfungsforschung gGmbH Institute for Communication and Assessment Research Wieblinger Weg 92a 69123 Heidelberg, Germany Web: www.ucan-assess.org

[Dmitriy Kopylenko]

Indeed, that might be a good idea to reuse a global DataSource for all Jdbc attributes repos. Currently it’s only possible if you have a globally defined JNDI-bound DataSource (but who does JNDI these days?) ;-) 

As could be seen here: https://github.com/apereo/cas/blob/master/support/cas-server-support-person-directory/src/main/java/org/apereo/cas/config/CasPersonDirectoryConfiguration.java#L215

a new DataSource is created, well again, unless you have globally defined JNDI Datasoure. So, currently JNDI is your only option.

Best,

D.

--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/ef1e988f-645f-72bf-7789-c7e8f36cf57b%40cares.institute.