IBM Support

PI63045: UNABLE TO CHANGE LOG LEVEL

Fixes are available

9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Unable to change  WAS log detail level.
    The problem happens when you have setTurkish locale setting
    on Linux or Generic JVM settings.
    For example on Linux if using LANG=tr_TR.iso88599. or
    set Generic JVM argument -Duser.language=tr
    -Duser.region=TR -Dfile.encoding=tr_TR.iso88599
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5.5 and V9.0, that set the locale *
    *                  settings to Turkish in their system or      *
    *                  using                                       *
    *                  Generic JVM arguments.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the Turkish locale is set on the   *
    *                      system or with Generic JVM arguments,   *
    *                      the                                     *
    *                      WebSphere Application Server log detail *
    *                      level cannot be changed.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When the Turkish locale is set on the system using
    "LANG=tr_TR.iso88599" or the Generic JVM arguments are set using
    "-Duser.language=tr -Duser.region=TR -
    Dfile.encoding=tr_TR.iso88599", and the WebSphere Application
    Server log detail level is changed, the following exception is
    thrown:
    Exception in thread "main" java.lang.IllegalArgumentException:
    Cannot parse this name: ?NFO
    at java.util.logging.Level.parse(Level.java:149)
    at
    com.ibm.ws.event.logging.hpel.LevelSample.main(LevelSample.java:
    15
    The issue happens, because the small letter "i" is converted to
    UPPERCASE as a CAPITAL letter "I" with a dot above in the case
    of the Turkish locale, which is the expected behaviour. Since,
    the UPPERCASE "I" has a dot above it, the String API method
    "toUpperCase()" fails to parse it, and throws the exception:
    IllegalArgumentException.
    This is a known issue for the Java String API, when the Turkish
    locale is set.
    

Problem conclusion

  • The issue was resolved by implementing the suggested fix
    provided by the Java String API documentation for method
    "toUpperCase()", which was to provide the default locale as
    ENGLISH as an argument to the method, such as,
    "toUpperCase(Locale.ENGLISH)".
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.11 and 9.0.0.2.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI63045

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-25

  • Closed date

    2016-09-07

  • Last modified date

    2016-09-07

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
14 October 2021