Tomcat database connection pools failing on start-up
Paul Hethmon
paul.hethmon at clareitysecurity.com
Wed Feb 18 12:39:42 EST 2015
So I should be able to catch and suppress this exception in the DB connector. I actually would think I am now, but it could be I’m not catching that particular error. The idea with the DB plugin was to always fail gracefully if the DB was not available.
Paul
> On Feb 18, 2015, at 12:29 PM, Wessel, Keith <kwessel at illinois.edu> wrote:
>
>
> Initial SessionFactory creation failed.org.hibernate.HibernateException: Could not find datasource
> Exception in thread "Thread-4" java.lang.ExceptionInInitializerError
> at net.clareitysecurity.shibboleth.db.SessionObjectDAOImpl$HibernateUtil.<clinit>(SessionObjectDAOImpl.java:375)
> at net.clareitysecurity.shibboleth.db.SessionObjectDAOImpl.openSession(SessionObjectDAOImpl.java:341)
> at net.clareitysecurity.shibboleth.db.SessionObjectDAOImpl.getExpiredSessions(SessionObjectDAOImpl.java:243)
> at net.clareitysecurity.shibboleth.storage.StorageCleaner.run(StorageCleaner.java:50)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.hibernate.HibernateException: Could not find datasource
> at org.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:56)
> at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124)
-----
Paul Hethmon
Chief Software Architect
paul.hethmon at clareitysecurity.com
More information about the users
mailing list