[
https://issues.apache.org/jira/browse/GEODE-9053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306642#comment-17306642
]
ASF subversion and git services commented on GEODE-9053:
--------------------------------------------------------
Commit 9314ee5782a0ac4f008c1b035599a29637b0d84b in geode-native's branch
refs/heads/develop from Blake Bender
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=9314ee5 ]
GEODE-9053: Decode EXCEPTION message from server (#771)
- No longer need to grovel server logs for this, which is a nice
improvement.
> Decode EXCEPTION message in gnmsg
> ---------------------------------
>
> Key: GEODE-9053
> URL: https://issues.apache.org/jira/browse/GEODE-9053
> Project: Geode
> Issue Type: Improvement
> Components: native client
> Reporter: Blake Bender
> Assignee: Blake Bender
> Priority: Major
> Labels: pull-request-available
>
> As a developer, I would like to be able to see the exception message (type,
> reason, and callstack) returned by Geode in the EXCEPTION message. This
> message is straightforward to decode: it has 2 parts, the first part is a
> serialized Java object which can just be ignored, and the second part is just
> a string containing the exception message.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
