Issue #2643: stackoverflow big sur eclipse debug

since we changed to big sur we have in eclipse a stack overflow on starting our application. The code where it happens (it is just the start) is (everything is unchanged compared to the before big sur time, the compiled app works as expected, we also tried different databases, all the same):

entityManagerFactory = Persistence.createEntityManagerFactory(rootPath+OBJECTDB_DBFILE);

the console output is:

Exception in thread "main" java.lang.StackOverflowError
at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:153)
at java.lang.StringCoding.decode(StringCoding.java:193)
at java.lang.String.<init>(String.java:426)
at java.lang.String.<init>(String.java:491)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.<init>(FileInputStream.java:138)
at java.io.FileInputStream.<init>(FileInputStream.java:93)
at com.objectdb.o.STH.A(STH.java:717)
at com.objectdb.o.CFG.g(CFG.java:353)
at com.objectdb.o.CFG.f(CFG.java:299)
at com.objectdb.o.STH.A(STH.java:725)
at com.objectdb.o.CFG.g(CFG.java:353)
at com.objectdb.o.CFG.f(CFG.java:299)
at com.objectdb.o.STH.A(STH.java:725)
at com.objectdb.o.CFG.g(CFG.java:353)
at com.objectdb.o.CFG.f(CFG.java:299)
at com.objectdb.o.STH.A(STH.java:725)
at com.objectdb.o.CFG.g(CFG.java:353)
at com.objectdb.o.CFG.f(CFG.java:299)
at com.objectdb.o.STH.A(STH.java:725)
at com.objectdb.o.CFG.g(CFG.java:353)
at com.objectdb.o.CFG.f(CFG.java:299)
at com.objectdb.o.STH.A(STH.java:725)
at com.objectdb.o.CFG.g(CFG.java:353)
at com.objectdb.o.CFG.f(CFG.java:299)
at com.objectdb.o.STH.A(STH.java:725)
at com.objectdb.o.CFG.g(CFG.java:353)
at com.objectdb.o.CFG.f(CFG.java:299)
at com.objectdb.o.STH.A(STH.java:725)
at com.objectdb.o.CFG.g(CFG.java:353)
at com.objectdb.o.CFG.f(CFG.java:299)
at com.objectdb.o.STH.A(STH.java:725)
at com.objectdb.o.CFG.g(CFG.java:353)
at com.objectdb.o.CFG.f(CFG.java:299)
at com.objectdb.o.STH.A(STH.java:725)
at com.objectdb.o.CFG.g(CFG.java:353)
at com.objectdb.o.CFG.f(CFG.java:299)
at com.objectdb.o.STH.A(STH.java:725)
at com.objectdb.o.CFG.g(CFG.java:353)
at com.objectdb.o.CFG.f(CFG.java:299)
at com.objectdb.o.STH.A(STH.java:725)
at com.objectdb.o.CFG.g(CFG.java:353)
...

as we can see now it is a problem of the file permissions of the objectdb database file. The behavior is changed compared to the osx version before

Thank you for this report. It may indicate an issue with access permission to the objectdb.conf (configuration) file rather than to the database file itself. Could you confirm that this is solved by changing the access permissions to the configuration file. Anyway, ObjectDB should produce a better error message in such cases.

we just changed the permissions of the database file itself

Interesting. However, the exception is clearly due to issues in reading the configuration file and not the database file. Although the ObjectDB jar file is minified and full original class names are missing in the stack trace, you can still see that if you look at the file and class names that are shown in this stack trace.