Hi, from what I see in the HSQLDB code, I believe that the problem can also occur in single-threaded applications. The ValuePoolHashMap methods are proteced and exclusively accessed through the ValuePool class, which uses synchronized access for all calls. Therefore the ValuePoolHashMap will never have concurrent thread aceess and would behave equally in single or multi-threaded applications.
StackOverflowError in Value Pool mechanism
Hi, we are getting a very similar StackOverflowError with our product using HSQLDB. We have tried several newer versions (2.3.3, 2.3.4 and now just last week 2.4.0) and the Error is always coming up after a few days of continious run. The last post suggest that the issue has been fixed but is it part of a release or only in SVN trunk? Here is the log trace that we are getting: java.lang.StackOverflowError at org.hsqldb.map.BaseHashMap.getAccessCountCeiling(Unknown Source) at org.hsqldb.map.BaseHashMap.clear(Unknown...