-
Notifications
You must be signed in to change notification settings - Fork 34
Open
Description
Environment Details
- EclipseStore Version: 2.1.3
- JDK version: 17
- OS: Linux SUSE
- Used frameworks: Spring, Vaadin
Describe the Issue
Due to a large Power Failure in our city one of our Java application (docker tomcat container) which uses eclipse store did not shutdown properly...
Now after booting up we get the following error on startup:
org.eclipse.store.storage.exceptions.StorageException: Non-deleted non-empty data file not found: channel 0, file 91283
at org.eclipse.store.storage.types.StorageFileManager$Default.validateStorageDataFilesLength(StorageFileManager.java:841) ~[storage-2.1.3.jar:?]
at org.eclipse.store.storage.types.StorageFileManager$Default.initializeStorage(StorageFileManager.java:884) ~[storage-2.1.3.jar:?]
at org.eclipse.store.storage.types.StorageChannel$Default.initializeStorage(StorageChannel.java:782) ~[storage-2.1.3.jar:?]
at org.eclipse.store.storage.types.StorageChannelTaskInitialize$Default.succeed(StorageChannelTaskInitialize.java:200) ~[storage-2.1.3.jar:?]
at org.eclipse.store.storage.types.StorageChannelTaskInitialize$Default.succeed(StorageChannelTaskInitialize.java:34) ~[storage-2.1.3.jar:?]
at org.eclipse.store.storage.types.StorageChannelSynchronizingTask$AbstractCompletingTask.synchronizedComplete(StorageChannelSynchronizingTask.java:78) [storage-2.1.3.jar:?]
at org.eclipse.store.storage.types.StorageChannelSynchronizingTask$AbstractCompletingTask.complete(StorageChannelSynchronizingTask.java:126) [storage-2.1.3.jar:?]
at org.eclipse.store.storage.types.StorageChannelTask$Abstract.processBy(StorageChannelTask.java:260) [storage-2.1.3.jar:?]
at org.eclipse.store.storage.types.StorageChannel$Default.work(StorageChannel.java:453) [storage-2.1.3.jar:?]
at org.eclipse.store.storage.types.StorageChannel$Default.run(StorageChannel.java:536) [storage-2.1.3.jar:?]
at java.base/java.lang.Thread.run(Thread.java:840) [?:?]
Is there a way to fix the Database or is it forever lost ? Are there practices to prevent such errors for the future ?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels