commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason (JIRA)" <j...@apache.org>
Subject [jira] [Created] (VFS-437) Program crashes when StackOverFlow Exception happens from pulling a softlinked directory that link to the directory that has the same name one level above
Date Mon, 17 Sep 2012 23:41:08 GMT
Jason created VFS-437:
-------------------------

             Summary: Program crashes when StackOverFlow Exception happens from pulling a
softlinked directory that link to the directory that has the same name one level above 
                 Key: VFS-437
                 URL: https://issues.apache.org/jira/browse/VFS-437
             Project: Commons VFS
          Issue Type: Bug
    Affects Versions: 2.0
         Environment: java version "1.7.0_02"
Java(TM) SE Runtime Environment (build 1.7.0_02-b13)
Java HotSpot(TM) 64-Bit Server VM (build 22.0-b10, mixed mode)

Linux version 2.6.18-238.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704
(Red Hat 4.1.2-48)) #1 SMP Thu Jan 13 15:51:15 EST 2011
            Reporter: Jason
            Priority: Blocker
             Fix For: 2.1


With the setting below, StackOverFlow exceptions occur and server crashes

Attept to pull with:
ftp://root:password@ip:/Vol1

Vol directory has the following info
lrwxrwxrwx  1 root root        5 Oct  5  2007 Vol1 -> /Vol1

set the builder.setUserDirlsRoot (opt, true)

When it tries to look for the parent of the Vol1, it goes back to the same Vol1, which causes
a infinite loop that eventually creates stackoverflow exception.

Exception is shown below
java.lang.StackOverflowError
	at org.apache.commons.net.ftp.FTPFile.isDirectory(FTPFile.java:116)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:334)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:496)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:344)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:496)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:344)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:496)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:344)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:496)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:344)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:496)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:344)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:496)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:344)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:496)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:344)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:496)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:344)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:496)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:344)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:496)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:344)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:496)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:344)
	at org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:496)
	at org.apache.commons.vfs2.provider.ftp.FtpFileObject.doGetType(FtpFileObject.java:344)



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message