Tomcat database connection pools failing on start-up

[Cantor, Scott]

On 2/18/15, 5:29 PM, "Wessel, Keith" <kwessel at illinois.edu> wrote:


>
>Yes, Tomcat does appear to start. The IDP, in fact, also starts. I looked 
>more at logs and was wrong about that. But since the session factory for 
>Hibernate couldn't be initialized because it points to my Tomcat 
>connection pool, Hibernate throws an exception after the user submits 
>their username and password which prevents the session from being created 
>or anything else from happening. The user gets a blank screen in their 
>browser.

That's more like what I would expect, though the blank screen sounds odd. 
Possibly a missed exception or something.

>Tomcat fails to initialize the database connection pool, then hibernate 
>fails to associate its resource with the non-existent pool. Here are the 
>logs. I'm no longer sure if this is something I should be configuring 
>around in Tomcat or something that needs to be coded around in the 
>DB-backed storage service.

If possible, you want the pool to init even if initial connections can't 
be obtained, but I'm not sure if dbcp can do that. Without that feature, 
this kind of problem at startup probably prevents it from recovering.

It's got nothing to do with the container, certainly.

Really it's two issues, whether the pool can recover (up to the pool) and 
what the error causes in the IdP.

-- Scott