-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 10.10-HF66, 2023.0, 2021.27
-
Component/s: Core MongoDB
-
Release Notes Summary:DocumentNotFound exception message always includes the doc id.
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform #70, nxplatform #71
-
Story Points:1
When loading document than cannot be read because of corruption or other reason, we have exception traces that are useless because they lack the document id:
org.nuxeo.ecm.core.api.DocumentNotFoundException: Unknown document type: CorruptedType at org.nuxeo.ecm.core.storage.dbs.DBSSession.getDocument(DBSSession.java:448) ~[nuxeo-core-storage-dbs-2021.26-SNAPSHOT.jar:?] at org.nuxeo.ecm.core.storage.dbs.DBSSession.getDocument(DBSSession.java:435) ~[nuxeo-core-storage-dbs-2021.26-SNAPSHOT.jar:?] at org.nuxeo.ecm.core.storage.dbs.DBSSession.getDocument(DBSSession.java:417) ~[nuxeo-core-storage-dbs-2021.26-SNAPSHOT.jar:?] at org.nuxeo.ecm.core.storage.dbs.DBSDocument.getParent(DBSDocument.java:324) ~[nuxeo-core-storage-dbs-2021.26-SNAPSHOT.jar:?] at org.nuxeo.ecm.core.api.DocumentModelFactory.createDocumentModel(DocumentModelFactory.java:72) ~[nuxeo-core-2021.26-SNAPSHOT.jar:?] at org.nuxeo.ecm.core.api.AbstractSession.readModel(AbstractSession.java:389) ~[nuxeo-core-2021.26-SNAPSHOT.jar:?]
Make sure the document uuid or path is always traced on such exception.
- is related to
-
-
- Resolved
-
