commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Eckenfels (JIRA)" <>
Subject [jira] [Commented] (VFS-617) isReadable fails if unable to determine group identity
Date Wed, 05 Apr 2017 07:54:41 GMT


Bernd Eckenfels commented on VFS-617:

I would agree that VFS-590 and VFS-617 have both the same cause (explicite checks) however
this here seems to be caused at a different operation (unfortunately the stack trace is not
complete so we don't know which, but it is more on login than on move)

I think I would make the check on login configurable and on move I would rely on failed operation
from server without pre-checking (or at least make the pre-check configurable as well). If
"isWriteable" can be implemented without, I am not sure. But not using those methods is not
only with VFS a good idea.

> isReadable fails if unable to determine group identity
> ------------------------------------------------------
>                 Key: VFS-617
>                 URL:
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: Windows 7 Java 7. Failure occured connecting via SFTP to a Synology
box running DSM 6.
>            Reporter: Tim Nickels
> The doIsReadable method of SftpFileObject throws an exception if the system cannot identify
group/owner permissions....... 
> Exception in thread "main" org.apache.commons.vfs2.FileSystemException: Could not determine
if file "sftp://myURI" is readable.
> 	at org.apache.commons.vfs2.provider.AbstractFileObject.isReadable(
> 	at com.avenca.vfs.VFSUtils.main(
> Caused by: com.jcraft.jsch.JSchException: Could not get the groups id of the current
user (error code: 1)
> 	at org.apache.commons.vfs2.provider.sftp.SftpFileSystem.getGroupsIds(
> 	at org.apache.commons.vfs2.provider.sftp.SftpFileObject.getPermissions(
> 	at org.apache.commons.vfs2.provider.sftp.SftpFileObject.doIsReadable(
> 	at org.apache.commons.vfs2.provider.AbstractFileObject.isReadable(
> The problem is the method is using 
> return getPermissions(true).isReadable()
> The folder *is* readable without these permissions, and so should be set to
> return getPermissions(false).isReadable()
> Which correctly allows the system to identify a readable folder without adding unnecessary

This message was sent by Atlassian JIRA

View raw message