PersistenceManager deserialization logging improvement#8962
Merged
mbien merged 1 commit intoapache:masterfrom Nov 7, 2025
Merged
PersistenceManager deserialization logging improvement#8962mbien merged 1 commit intoapache:masterfrom
mbien merged 1 commit intoapache:masterfrom
Conversation
matthiasblaesing
approved these changes
Nov 7, 2025
Contributor
matthiasblaesing
left a comment
There was a problem hiding this comment.
Looks sane to em.
Don't dump the serialized form on DataObjectNotFoundException when a TopComponent can't be deserialized. This is often harmless and happens for example when an opened project moved while NB was closed. A single warning line should be sufficient. Full exception is logged with FINE level.
0e7d7d8 to
892e14c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Don't dump the serialized form on
DataObjectNotFoundExceptionwhen aTopComponentcan't be deserialized. This is often harmless and happens for example when an opened project moved while NB was closed. A single warning line should be sufficient.Full exception is logged with
FINElevel.example log line:
open project -> close NB -> remove project -> start NB
as sidenote:
the original stack dump had several lines which just said "msg". Those were ResourceBundle keys which weren't substituted with the actual message. But substituting it might cause more harm than good (given the key name). I haven't seen this anywhere else so far. My guess is that the mechanism isn't used very often. In any case the hotfix would look like:
Details