Tomcat database connection pools failing on start-up

[Wessel, Keith]

Actually, Scott, if I understand Paul's note correctly, catching the exception would help. The IDP wouldn't run and fail. It would just run without saving sessions to the database. Unclustered IDPs are better than IDPs that present a blank screen after login.

Paul, would you like me to file a bug on this?

And if anyone knows how to tell Tomcat dbcp to keep trying instead of failing if the database server's unavailable on start-up, I'd love to know.

Thanks, Scott and Paul.

Keith


-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Wednesday, February 18, 2015 11:50 AM
To: Shib Users
Subject: Re: Tomcat database connection pools failing on start-up

On 2/18/15, 5:39 PM, "Paul Hethmon" <paul.hethmon at clareitysecurity.com> 
wrote:



>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.

It's probably a runtime error. The problem is more with the fairly broken 
error handling in V2, there are just too many broken code paths in there.

But even if you catch it, that just leaves the IdP running and failing 
endlessly until restart unless the pool can init without preloading 
connections.

-- Scott

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