Tomcat database connection pools failing on start-up

[Wessel, Keith]

Hi, all,

We're running the database-backed storage service, and it's working very well, even allowing the IDP to continue to run unclustered when our database server's down. Problem we have, though, is when the database server is down and Tomcat starts. This happened this morning as the database server was down for patching when the IDP nodes were restarted after patching.

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? :)

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?

Thanks,
Keith