DonalEvans commented on pull request #6631:
URL: https://github.com/apache/geode/pull/6631#issuecomment-866189691
Correct me if I'm wrong, but isn't the exception message that you're adding
to the `GemFireIOException` already visible in the exception stack trace? With
the changes here:
```
org.apache.geode.SerializationException: Serialization failed (
java.lang.Object )
at
org.apache.geode.internal.cache.GemFireCacheImpl.registerPdxMetaData(GemFireCacheImpl.java:5156)
...
Caused by: java.io.NotSerializableException: java.lang.Object <<< HERE
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
...
```
and without the changes:
```
org.apache.geode.SerializationException: Serialization failed
at
org.apache.geode.internal.cache.GemFireCacheImpl.registerPdxMetaData(GemFireCacheImpl.java:5156)
...
Caused by: java.io.NotSerializableException: java.lang.Object <<< HERE
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)
...
```
Are there places where the logged exception doesn't contain the exception
stack? If so, I would suggest that the problem is with those places, not with
the exception itself.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
