-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[mapdb] ClassNotFoundException on activation "org.openhab.persistence.mapdb.internal.MapDBitemSerializer cannot be found" #8794
Comments
I ran into the same issue and it looks like the mapdb in OH3 cannot read/write to mapdb files that were previously generated by OH2. After deleting the OH2 mapdb files it worked again for me. |
Works here, too. Thanks! |
That would be nice but I investigated the issue and it looks like the way how data is serialized in the new OH3 mapdb implementation also changed from plain strings to JSON. 😐 So unless that changes it will be difficult to support a seamless migration where all OH2 mapdb data can be used. But it would already help to catch the exception and either print a helpful message or rename/delete the DB file and log that a new database is used due to incompatibilities. |
The only way to recover from an incompatible OH2 database is create a new database. With these changes the add-on will create a new database automatically and archive the incompatible database files in a backup directory. Fixes openhab#8794 Signed-off-by: Wouter Born <[email protected]>
The only way to recover from an incompatible OH2 database is to create a new database. With these changes the add-on will create a new database automatically and archive the incompatible database files in a backup directory. Fixes openhab#8794 Signed-off-by: Wouter Born <[email protected]>
The only way to recover from an incompatible OH2 database is to create a new database. With these changes the add-on will create a new database automatically and archive the incompatible database files in a backup directory. Fixes openhab#8794 Signed-off-by: Wouter Born <[email protected]>
The only way to recover from an incompatible OH2 database is to create a new database. With these changes the add-on will create a new database automatically and archive the incompatible database files in a backup directory. Fixes openhab#8794 Signed-off-by: Wouter Born <[email protected]>
The only way to recover from an incompatible OH2 database is to create a new database. With these changes the add-on will create a new database automatically and archive the incompatible database files in a backup directory. Fixes openhab#8794 Signed-off-by: Wouter Born <[email protected]>
The only way to recover from an incompatible OH2 database is to create a new database. With these changes the add-on will create a new database automatically and archive the incompatible database files in a backup directory. Fixes #8794 Signed-off-by: Wouter Born <[email protected]>
The only way to recover from an incompatible OH2 database is to create a new database. With these changes the add-on will create a new database automatically and archive the incompatible database files in a backup directory. Fixes openhab#8794 Signed-off-by: Wouter Born <[email protected]>
I get this error on openhab 3 m1 and latest snapshot build #1973. No values are restored.
The text was updated successfully, but these errors were encountered: