Details
-
Bug
-
Resolution: Answered
-
Low
-
4.4.1
-
None
-
Severity 3 - Minor
-
Description
Summary
sun.jnu.encoding is not explicitly defined in the startup of the FishEye JVM, and so it's possible for this to be set to an unexpected value in a customer's environment which causes issues with extended UTF-8 characters, e.g. working with Chinese text in a file
Steps to Reproduce
- Have your environment set up with sun.jnu.encoding as GBK by default
- Create a file containing special characters
Expected Results
Even if your JVM is configured like that by default, FishEye server should force it to be UTF-8.
Actual Results
Chinese text does not appear correctly in FishEye/Crucible.
Workaround
Set sun.jnu.encoding explicitly to UTF-8 in the $FISHEYE_OPTS Environment variables:
-Dsun.jnu.encoding=UTF-8