[
https://issues.apache.org/jira/browse/GEODE-9406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Blake Bender updated GEODE-9406:
--------------------------------
Description:
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:
"Value":
{ "Size": 401767, "IsObject": 1 }
,
"ERROR": "Exception reading message - probably incomplete"
}
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:
```
"Value": {
"Size": 401767,
"IsObject": 1,
"Data":
{ "DSCode": "PDX", "Value": "<<Unreadable - no type info available in gnmsg>>" }
},
"EventId":
{ "Data": "Unavailable - message is too long" }
```
was:
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:
```
"Value": {
"Size": 401767,
"IsObject": 1
},
"ERROR": "Exception reading message - probably incomplete"
}
```
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:
```
"Value": {
"Size": 401767,
"IsObject": 1,
"Data": {
"DSCode": "PDX",
"Value": "<<Unreadable - no type info available in gnmsg>>"
}
},
"EventId": {
"Data": "Unavailable - message is too long"
}
```
> 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
> Priority: Major
>
> 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:
>
> "Value":
> { "Size": 401767, "IsObject": 1 }
> ,
> "ERROR": "Exception reading message - probably incomplete"
> }
>
> 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:
> ```
> "Value": {
> "Size": 401767,
> "IsObject": 1,
> "Data":
> { "DSCode": "PDX", "Value": "<<Unreadable - no type info available in
> gnmsg>>" }
> },
> "EventId":
> { "Data": "Unavailable - message is too long" }
> ```
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
