Replies: 1 comment 3 replies
-
We see the same problem here and don't really know what we can do. Unfortunately, the level of information is so low that we can't even begin to research the causes. I would also be very open to suggestions |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am currently facing the issue that my data got somehow corrupted. The StorageManager tries to load an entity wih an Oid that it can't find leading to a crash on application startup.
The stacktrace:
From what I read this should never happen and is a bug. I was not able to identify any bug in my service since it is not very complex and only has some CRUD stuff in it.
So my next idea was to just run the garbage collection manually but the garbage collection does pretty much the same check, marks the oid as zombie and continues. The default impl of org.eclipse.store.storage.types.StorageGCZombieOidHandler (which is supposed to handle such an event) also does nothing.
Has anybody else had this issue and found the root cause or maybe a way to deal with it so I can start my application again without overwriting the Exception?
Beta Was this translation helpful? Give feedback.
All reactions