-
Bug
-
Resolution: Fixed
-
P3
-
8, 9
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8171166 | 9 | Kevin Walls | P3 | Resolved | Fixed | b150 |
| JDK-8183869 | 8u161 | Kevin Walls | P3 | Resolved | Fixed | b01 |
| JDK-8171372 | 8u152 | Kevin Walls | P3 | Resolved | Fixed | b04 |
| JDK-8192683 | emb-8u161 | Kevin Walls | P3 | Resolved | Fixed | b01 |
UsageTracker using the UDP logging transport can, in very extreme
cases, have a truncated record as the packet is full. The example observed by a customer is a huge app name/URL with many details.
Only the initial part of the app name would be needed to recognise the app.
A truncated record could be recognised as it does not end with a \n but such records are incomplete and harder to parse, as they can have missing fields.
cases, have a truncated record as the packet is full. The example observed by a customer is a huge app name/URL with many details.
Only the initial part of the app name would be needed to recognise the app.
A truncated record could be recognised as it does not end with a \n but such records are incomplete and harder to parse, as they can have missing fields.
- backported by
-
JDK-8171166 UsageTracker should limit records and avoid truncation
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-