Today I discovered the if I set the defaultQueryTimeout instead of the socketTimeout setting then I can workaround this problem. I daresay, however, that Hibernate should still circumvent this situation by releasing the connection from the pool in case the socketTimeout is set.