directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <>
Subject [jira] [Commented] (DIRSERVER-1646) Locale problem on startup (Apache DS 2.0.0-M2)
Date Thu, 25 Aug 2011 09:48:29 GMT


Pierre-Arnaud Marcelot commented on DIRSERVER-1646:

OK, I found the cause of the issue.

This is due to the fact we're using the String.toLowerCase() method in various places and
that as stated in its javadoc, it can cause issues with various locales and especially the
Turkish locale.

Here the specific note from the javadoc:
Note: This method is locale sensitive, and may produce unexpected results if used for strings
that are intended to be interpreted locale independently. Examples are programming language
identifiers, protocol keys, and HTML tags. For instance, "TITLE".toLowerCase() in a Turkish
locale returns "t\u0131tle", where '\u0131' is the LATIN SMALL LETTER DOTLESS I character.
To obtain correct results for locale insensitive strings, use toLowerCase(Locale.ENGLISH).

In our case 'I' characters get translated to lower dotless 'i', which is then causing a lot
of issue in parts of code where we don't expect such a character.

In order to fix that we need to verify our use of the String.toLowerCase() method and we might
need to replace it by String..toLowerCase( Locale.ENGLISH ) as it is mentionned in the javadoc.

> Locale problem on startup (Apache DS 2.0.0-M2)
> ----------------------------------------------
>                 Key: DIRSERVER-1646
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M2
>         Environment: Windows Vista Basic 32-bit on Asus X59SR Laptop; installed with
the Windows installer; OS language is EN while the region is TR
>            Reporter: Deniz Acay
>            Assignee: Pierre-Arnaud Marcelot
>             Fix For: 2.0.0-M3
>         Attachments: apacheds.log, wrapper.log
> Similar to DIRSERVER-1645, but no exception log was found and the startup failed immediately.
Added these to wrapper.conf and the service could be started:

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message