jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-1015) BlobStore.putBlob throws RuntimeException with filesystem provider on localized Windows
Date Thu, 15 Oct 2015 22:45:06 GMT

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

Andrew Gaul commented on JCLOUDS-1015:
--------------------------------------

[~halvdanhg] Can you post the backtrace from the exception?  In particular I would like to
see which {{File}} call generates an errors since jclouds does not do anything interesting
with the file system other than setting extended attributes.  Since you may be the only one
who can reproduce these symptoms could you investigate a workaround within filesystem, possibly
using the nio.2 FileSystem API instead?

> BlobStore.putBlob throws RuntimeException with filesystem provider on localized Windows
> ---------------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-1015
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1015
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.9.1
>         Environment: Microsoft Windows (tested on 7 and 10), Java 7 and 8.
>            Reporter: Halvdan Hoem Grelland
>            Assignee: Zack Shoylev
>            Priority: Minor
>              Labels: filesystem, windows
>
> When using the filesystem provider on a localized 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 'Everyone' user group using UserPrincipalLookupService.lookupPrincipalByName.
> Turns out the 'Everyone' group/user is only actually available on Windows systems set
to an English locale, whilst other locales will likely have localized names for the group
(tested on Norwegian Windows in which the Everyone group is known as "Alle").
> The only ubiquitous reference to any of the built-in groups or users on a Windows system
are the SIDs. For example, 'Everyone' is known as 'S-1-1-0'. 
> Unfortunately, the API exposed in java.nio.file doesn't accept SIDs for lookup, meaning
there is, as far as I can tell, no pure Java solution to resolving the UserPrincipal without
knowing the (localized) name.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message