From b1e5b659c1cc9605eb086a4731339319425c4ee5 Mon Sep 17 00:00:00 2001 From: Tudor Malene Date: Wed, 6 Nov 2019 17:04:05 +0000 Subject: [PATCH] ENT-4107: Document blob inspector issue (#5685) * ENT-4107 - document issue with enums in the blob inspector (#5685) * ENT-4107 - fixed formatting --- docs/source/blob-inspector.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/source/blob-inspector.rst b/docs/source/blob-inspector.rst index cffa40118b..4701913f87 100644 --- a/docs/source/blob-inspector.rst +++ b/docs/source/blob-inspector.rst @@ -91,6 +91,17 @@ Here's what a node-info file from the node's data directory may look like: Notice the file is actually a serialised ``SignedNodeInfo`` object, which has a ``raw`` property of type ``SerializedBytes``. This property is materialised into a ``NodeInfo`` and is output under the ``deserialized`` field. + +Classpath +~~~~~~~~~ + +If you run the blob inspector without any JAR files on the classpath, then it will deserialize objects using the Class Carpenter (see :doc:`serialization` for details). +The reason for this is that the types are not available, so the serialization framework has to synthesise them. + +.. note:: This mechanism works fine in most situations, but there is one known issue when the serialized blob contains an ``enum``. + In this case you will get this exception ``java.lang.NoClassDefFoundError: Could not initialize class _YourEnum_``. + To solve this problem, you must add the JAR file that contains the ``enum`` to the classpath of the blob inspector. + Command-line options ~~~~~~~~~~~~~~~~~~~~