You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2018/11/03 21:07:00 UTC

[jira] [Commented] (JCLOUDS-1423) BlobStore.putBlob throws RuntimeException with filesystem provider on RUSSIAN localized Windows

    [ https://issues.apache.org/jira/browse/JCLOUDS-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674209#comment-16674209 ] 

Andrew Gaul commented on JCLOUDS-1423:
--------------------------------------

Could you share the exception backtrace?  I suspect that if you add some logging to {{Utils.getWindowsEveryonePrincipalName}} you may be able to debug this further.  Unfortunately I do not use Windows and don't speak Russian so you may need to fix this yourself.

> BlobStore.putBlob throws RuntimeException with filesystem provider on RUSSIAN localized Windows
> -----------------------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-1423
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1423
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 2.0.2
>         Environment: Microsoft Windows (tested on 7 and 10), Java 7 and 8.
>            Reporter: Gunther Wiest
>            Assignee: Zack Shoylev
>            Priority: Minor
>              Labels: filesystem, windows
>             Fix For: 2.1.0, 2.0.1
>
>
> When using the filesystem provider on a localized RUSSIAN Windows system putBlob consistenly throws a RuntimeException. The put operation does succeed, however, meaning a viable workaround is to catch-and-ignore.
> The cause of the Exception is a UserPrincipalNotFoundException which is thrown in org.jclouds.filesystem.util.Utils while trying to resolve the Windows SID 'S-1-1-0' user group using UserPrincipalLookupService.lookupPrincipalByName.
>  
> The Russian translation for everyone is "Все", and the output of the "whoami" command will be in [https://de.wikipedia.org/wiki/Codepage_866] wich turns into different characters, when read into a java string via "ProcessBuilder.start". This is the reason why the "lookupPrincipalByName" fails.
> This will occur on all windows systems, where the translation contains non standard ASCII 7 bit characters. See also  [https://www.microsoft.com/en-us/language/Search?&searchTerm=Everyone&langID=Russian&Source=true&productid=All%20Products] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)