The problem was an offline custom endpoint. It wasn't part of our metadata scan as we were specifying a specific catalog and schema, but if any part of your instance is down, the jdbc driver will fail the metadata call. The solution was to create a service account that wasn't assigned to that endpoint. I know I'm getting some of the terminology mixed up, but that's the general idea.