Shibboleth 5.1.4 Uncaught java.lang.NullPointerException

[Cantor, Scott]

It's certainly a bug in that driver, any NPE would be. We should still be catching it somewhere and assuming all drivers are broken since they more or less are.

There's no way to catch it that wouldn't already be catching it if anything were.

My general experience with JDBC is that its networking code can't be trusted and remote JDBC doesn't work, and I don't do them as a consequence, mine are all localhost caches.

Obviously YMMV, but at the end of the day...I'm right because if I wasn't, these kinds of issues wouldn't keep happening. It's just not within our power to solve that, and even if/when we catch that NPE, once you start catching stuff like that, you tend to only delay the inevitable in terms of stability of that layer of code.

But we will accept the bug of not guarding it where we can, if we can. It must be getting thrown in the mainline logic somewhere that we'd catch if it's showing up to users.

-- Scott