Why is ObjectDb is holding onto classes that no longer exist? 

#1

Why ObjectDb is holding onto classes that no longer exist?  You can see the classes in the obj-reflection.log.  I've included all of my java models in the models.zip file.

As far as I can tell, it's not causing any problems,   so feel free to tell me to take a hike, but I hate having unexplained exceptions in logs as they tend to bite you in the long term...

       Thanks!

             Emily

excerpt from log:
[2019-09-30 17:19:13 #1 type.loader] 
java.lang.ClassNotFoundException: models.Strack$Status
    at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

#2

The ObjectDB database keeps information on classes even after they are no longer in use. Currently the only way to such classes them from the database is to create a new database (although this will probably change in some future version).

The log file indicates that these log entries are not created during normal use of ObjectDB but when the Doctor is run, and can be ignored.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#3

Cool! Thanks a million for the reassurance. Is there any easy way to port all the data in my database to a new one or do you recommend just leaving the problem...

#4

You may just ignore it for now as porting data to a new database will require writing a program that read all the objects from one database and store them in another new database.

ObjectDB Support
ObjectDB - Fast Object Database for Java (JPA/JDO)
#5

Thanks for everything! I will just ignore it then...


Post Reply

To post a reply and/or subscribe to update notifications - please login