The amount of detail in these DB exceptions is perhaps less ideal than it could be? Maybe?

a smidgen more details might help, this is close to the classic client email, "there's a error"

This is from a connection timeout. We've got a bunch of

<cfquery>

call failures, and we've been diligently logging the exception detail, and we have a bunch of... empty strings and zeros to deal with. (It's a generic exception handler, so doesn't know about any additional exception properties that might be getting returned - and I accept this is less than ideal - but message and detail should be present and useful information on any exception, right?)

top of the java stacktrace and any caused by are very helpful

yeah not in this case. That's all generic "DB shit went wrong" rather than "yeah it timed out" Anyway yeah, more info is reachable. My point was that the starting point should be

message

and

detail

. And then work from there.