JDK-8030103 : Java Usage Tracker: need to escape separator chars
  • Type: Bug
  • Component: core-svc
  • Sub-Component: tools
  • Affected Version: 8
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2013-12-13
  • Updated: 2014-07-29
  • Resolved: 2014-03-25
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.
JDK 8 JDK 9
8u20Fixed 9 b08Fixed
Related Reports
Duplicate :  
JDK-8031094 - UsageTracker loses quotes on command-line VM arguments.
Relates :  
JDK-8043887 - Multiple applet jars are reported to Java Usage Tracker incorrectly
Description
Java Usage Tracker uses "," as a separator char by default. It works fine in most cases, but sometimes the char can appear inside the fields. For example, if javac is launched with debug options, the "AppName" field will be

com.sun.tools.javac.Main -g:source,vars,lines ...

Other fields are very likely to contain commas as well. In all these cases, the separator char must be escaped.
Comments
Have a scheme for quoting in mind: If a field contains a separator, it needs quoting with " If an item in a field which is a list, like VM args, contains a space, that item should be single quoted with ' When adding quotes, any existing quote should be "doubled up", so a field containing " becomes "" Quotes customisable by an additional property in the usagetracker.properties file. The best thing I think is that this then imports simply into e.g. LibreOffice spreadsheets, which is part of the intent of these files. A parser is not too complicated, I have made one as awk is no longer simple to use to count the fields, so will likely include the parser as part of the updated testcase.
24-01-2014
We can update to Likelihood: M, Workaround: H, giving P3. I don't think we could increase likelihood or impact any more though.
07-01-2014