[jira] Commented: (HARMONY-5476) [classlib][luni] Harmony is unable to detect correct time zone on Linux

["Alexei Zakharov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HARMONY-5476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568638#action_12568638 ] 

Alexei Zakharov commented on HARMONY-5476:
------------------------------------------

I discovered that on some Linux distributions DRLVM is unable to detect time zone at all. I faced it on Fedora Core 7. I don't know the exact reason of this but it set user.timezone to empty string there. I created and committed a fallback code at r627506. It simply tries to detect the time zone by means standard API (from "time.h") in case if JVM failed to set "user.timezone" system variable.

> [classlib][luni] Harmony is unable to detect correct time zone on Linux
> -----------------------------------------------------------------------
>
>                 Key: HARMONY-5476
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5476
>             Project: Harmony
>          Issue Type: Bug
>          Components: Classlib
>         Environment: Linux32
>            Reporter: Alexei Zakharov
>            Assignee: Alexei Zakharov
>
> On Linux auto detection of default time zone works incorrectly. For example SimpleDateFormat always returns GMT +0 by default. This leads to incorrect work of some applications - Clock demo applet from RI distribution could be one of such examples. Please see the test case below:
> DateTest.java
> ---
> import java.text.SimpleDateFormat;
> import java.util.TimeZone;
> public class DateTest {
>     public static void main(String argv[]) {
>         SimpleDateFormat formatter;
>         formatter = new SimpleDateFormat();
>         System.out.println(formatter.getTimeZone().getDisplayName(
>                 true, TimeZone.SHORT) + ", " +
>                 formatter.getTimeZone().getDisplayName(true, TimeZone.LONG));
>     }
> --
> On RI (my workstation is located in Moscow, GMT+3):
> MSD, Moscow Daylight Time
> on Harmony (r619813):
> GMT+00:00, GMT+00:00
> However, on Windows Harmony correctly sets time zone to GMT +3. So this is a UNIX-only issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.