IBM Support

PM76855: Date format for query result set may not display due or produce status 500 error on localized CMservers, affecting OSLC/REST

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When working with date_time field values in IBM Rational
    ClearQuest over OSLC, the Date format for query result set may
    not display or produce status 500 errors on CM Servers that are
    localized to non-English numbering systems when using OSLC/REST.
    
    To reproduce:
    1. On any Windows host that has ClearQuest Web 7.1.2.8
    installed, change the locale [Windows Control Panels ? Windows
    Regional and Language Options ? Standards and formats setting]
    to French (Canada), Chinese, German, etc.
    Note: The long date format has no 'day in week' in it.
    2. Restart CM Server.
    3. Send an OSLC request to retrieve a date_time field, such as
    Submit_Date of a Defect record.
    4. The response contains the error in French Canadian for
    example:
    ?message?Unparseable date: 'jeu. juin 15 00:00:00 Heure avanc?e
    de l?Est (?UA) 2000'?/message?
    
    The symptom in Chinese, Korean and other language systems is the
    same, but the date string is translated into the corresponding
    language. So the date string in the error message has the same
    format which is '(day in week/name), month/name (day in month)
    time (time zone) year'. Such format is not used in either China,
    Korea, French Canadian, etc.
    
    Workaround if English is acceptable:
    1. On Windows, set the locale to English(US) before starting up
    CM Server.
    2. On Linux, set LC_ALL=en_US.utf8 before starting up CM Server.
    3. On both Windows and Linux, add WebSphere JVM parameter
    '-Duser.language=en -Duser.region=US' via Application servers ?
    server1 ? Process Definition ? Java Virtual Machine ? General
    JVM parameters.
    
    Changing the locale (on Linux setting LC_ALL=en_US.utf8) also
    changes the error messages from CM Server to English (which may
    or may not be acceptable).
    
    Looking back at past versions:
    Desired behavior in CQ 7.1.2.3 with French Canadian locale:
    ?cq:Submit_Date?2000-06-15T04:00:00Z?/cq:Submit_Date?
    
    Problem in 7.1.2.8:
    ?Error?
            ?message?Unparseable date: 'jeu. juin 15 00:00:00 Heure
    avanc?e de l?Est (?UA) 2000'?/message?
            ?statusCode?500?/statusCode?
    ?/Error?
    
    The following example OSLC request can be used to reproduce the
    issue against the SAMPL Defect Tracking Database:
    http://host/cqweb/oslc/repo/7.0.0/db/SAMPL/simpleQuery/16777224?
    oslc.select=cq:Submit_Date
    ??Look for the statusCode/error.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    ClearQuest Web users on some non-English locales receive a
    error message when requesting a date time field using a OSLC
    request like the following:
    "http://9.32.253.123/cqweb/oslc/repo/7.0.0/db/SAMPL/simpleQu
    ery/16777224?oslc.select=cq:Submit_Date"
    

Problem conclusion

  • A fix is available in ClearQuest 7.1.2.9 and 8.0.0.5.
    
    When calling OSLC requests as in the above example,
    ClearQuest Web query result sets are correctly displayed on
    all locales.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM76855

  • Reported component name

    CLEARQUEST UNIX

  • Reported component ID

    5724G3601

  • Reported release

    712

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-09

  • Closed date

    2012-12-15

  • Last modified date

    2012-12-15

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    CLEARQUEST UNIX

  • Fixed component ID

    5724G3601

Applicable component levels

  • R712 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.2","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 December 2012