This content has been marked as final. Show 3 replies
This looks like a bug in JE -- thanks for reporting it! I'm still investigating, but it looks like a bug that impacts both the Serializable and ReadCommitted isolation modes. We'll fix this.
In the mean time, you can work around this problem by setting the timeouts for the entire environment using the EnvironmentConfig.setLockTimeout and setTxnTimeout methods. Will this work for you? Or do you need different timeout values for different transactions?
Hello MarkGood to hear!
Yes, the workaround works fine, thanks.
By the way: do you have some release-roadmapNo, unfortunately. Like in many large companies, our lawyers and accountants won't allow us to do that. BDB is available under a commercial license as well as an open-source license.
published (when are the next patches/releases