[
https://issues.apache.org/jira/browse/GEODE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17371673#comment-17371673
]
ASF subversion and git services commented on GEODE-9406:
--------------------------------------------------------
Commit f261b10877bcd4f09f1af373d005d400fd4e2c4b in geode-native's branch
refs/heads/develop from Blake Bender
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=f261b10 ]
GEODE-9406: Report DSCode (type) for PDX values in gnmsg (#827)
> gnmsg should log type etc of long values, if it can decode them
> ---------------------------------------------------------------
>
> Key: GEODE-9406
> URL: https://issues.apache.org/jira/browse/GEODE-9406
> Project: Geode
> Issue Type: Improvement
> Components: native client
> Reporter: Blake Bender
> Assignee: Blake Bender
> Priority: Major
> Labels: pull-request-available
>
> The geode-native logger has a hard limit of 8KB for log strings, so for
> client logs with large values (typically PUT messages with large objects like
> PDX instances), the hex dump of the message in the log file will be truncated
> and thus not fully decodable. The current version of `gnmsg` generically
> catches exceptions due to truncated messages at top-level, and outputs JSON
> that looks something like this:
> {code:java}
> "Value": {
> "Size": 401767,
> "IsObject": 1
> },
> "ERROR": "Exception reading message - probably incomplete"
> } {code}
>
> For `PUT` messages, at least, we can do slightly better, and at least dump
> the type of the value in the message, which is probably of interest. Here's
> an example:
> {code:java}
> "Value": {
> "Size": 401767,
> "IsObject": 1,
> "Data": {
> "DSCode": "PDX",
> "Value": "<<Unreadable - no type info available in gnmsg>>"
> }
> },
> "EventId": {
> "Data": "Unavailable - message is too long"
> }
> } {code}
> We should dump all of this info, if we can decode it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
