 2 | , until a user that still has the old version of the class accesses the database. Please verify ... classes that you mentioned. Could you please try the last ObjectDB version (2.5.3_03) to verify |
2 | changes - on order to verify that the new problems are caused by the new changes. New build works OK ... the fix of #9, which is now disabled. Do you have a new heap dump to verify that this is the same problem |
2 | then your configuration file is not used. In addition, please verify that you close the database ... - is this the wrong location? > In addition, please verify that you close the database |
2 | and in which false? In addition, verify that the same EntityManager is used. If you can write ... seems to work well with 2.0.5 at least on my computer. Please verify that you switched the server |
2 | in advance for your help. Best wishes, The BTC-ES Team Please verify that all your classes ... your application use many different databases? single class loader or multiple class loaders? Please verify |
1 | 500Mb ObjectDb database opening issue |
1 | using a new server version (2.4.3_07) with an old client version. Please verify that you are using the same version also on the client side. hadnosoul |
1 | to your schema may cause a similar exception. Please verify that an activation code |
1 | and small database, and provide exact instructions (that have been verified by you first |
1 | classes (you should use enhanced classes anyway to improve performance). Verified and confirming that 2.2.8_01 fixes the issue. kaosko |
