Tomcat database connection pools failing on start-up

[Charles R. Tompkins]

We use tomcat and notice that the IdP (2.4) cannot initialize when the database infrastructure is unavailable.  Tomcat tries a quick connect when initializing the data connector on IdP startup.

We monitor the idp-process.log for several different kinds of SQL errors which appear at times, including this failed initialization attempt.

Of course, tomcat is still running.

-Charles


-----Original Message-----
From: Cantor, Scott [cantor.2 at osu.edu]
Received: Wednesday, 18 Feb 2015, 11:17AM
To: Shib Users [users at shibboleth.net]
Subject: Re: Tomcat database connection pools failing on start-up


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


>
>We're using a Tomcat resource for the database connection pool. Does
>anyone know of any way to tell Tomcat it can continue running and start
>the IDP even when a resource like that is unavailable? Or do I just have
>to tell our sysadmins not to restart the server if the database server is
>down? :)

I'm surprised Tomcat would care, and it doesn't really know anything about
pooling, that's just a function of the data source. It's more likely to do
with the pool configuration itself, I imagine.

>If Jetty handles this situation better, BTW, this could be my excuse to
>switch. I'm planning on doing that, anyway, for my IDP V3 move later this
>year. Does anyone know if it does?

I don't really know. I'm not clear what Tomcat's doing with it. Does
Tomcat itself not start, or is it just the IdP not starting?

-- Scott

--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net