Community
Participate
Working Groups
When log files containing Japanese characters are imported into the Log View using Log and Trace Analyzer on a Japanese machine, the Japanese characters are omitted from the event data and therefore not shown in the Log view. This problem was found by downstream products that have static parsers for logs such as DB2 and Oracle logs. However, it will probably affect rules based parsers as well. The problem is in the GLA runtime code. If the character set is not specified in the Context configuration in the adapter file, the GLA hard codes the characters set to be used to read the log file as UTF-8 on all platforms except z/OS where it hardcodes IBM-1047. This is incorrect behaviour because it doesn't support native DBCS encodings. The GLA should use the default JVM character set encoding by default to read log files which can then be overridden by the setting in the Context Instance configuration in the adapter file. This will affect both static and rules-based parsing because common code is used to read the log file.
This should be fixed in 3.3
Created attachment 17212 [details] CommonBaseEvent log file containing Japanese characters The third, fifth and sixth records contain Japanese characters.
The attached CommonBaseEvent XML log file can be imported on a Japanese machine to show this behavior - no Japanese characters will be shown in the Log View.
Fix committed to Head - in Context.update() set the charset to the file.encoding system property value if it exists.
Created bugzilla 83629 to change the documentation to reflect this fix.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
