Closed DxsSucuk closed 10 months ago
I doubt this is a HikariCP issue. Was it working without any problem before "the past weeks", and if so, what changed in that time?
It did, it seems like by either upgrading Hibernate or or Hikari they no longer like to work with Springboot? When I first encountered this Issue, I was able to fix it by reverting to a older Hibernate version. But now after updating Hikari its not a big fan.
Closing this Issue, since after even more testing it seems like this has nothing to do with Springboot and Hikari in itself. But rather Hibernate or something misconfigurated on my end.
If anyone seems to have the same Issue I opened a discussion on the Hibernate Forum. https://discourse.hibernate.org/t/hibernate6-with-hikaricp-on-springboot-fails-to-boot/8614/7
As a workaround downgrading to Hibernate 6.2.9 seems to work.
For the past weeks Springboot can no longer seem to find the right JDNI name of Hikari? Error message:
Springboot config:
Pom (from the dependency which provides all the stuff)
Is there anything I missed that might cause this issue or?