I no longer work at the company where I ran into this issue. Last I heard, they were applying this patch and custom building hibernate to avoid the problem. As far as I'm concerned you can close this jira issue.