JDK-8164843 : UsageTracker should limit records and avoid truncation
- Type: Bug
- Component: core-svc
- Sub-Component: tools
- Affected Version: 8,9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2016-08-26
- Updated: 2017-11-29
- Resolved: 2017-02-15
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 10 | JDK 8 | JDK 9 |
|---|---|---|
10Fixed  |
8u152Fixed |
9Fixed |
Description
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.
Comments
|