commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Giel (JIRA)" <j...@apache.org>
Subject [jira] Commented: (NET-140) FTPClient listFiles returns incorrect timestamp on freshly uploaded file but corrects itself after about 15 minutes
Date Sat, 14 Oct 2006 02:50:25 GMT
    [ http://issues.apache.org/jira/browse/NET-140?page=comments#action_12442214 ] 
            
Bill Giel commented on NET-140:
-------------------------------


   [[ Old comment, sent by email on Sun, 03 Sep 2006 01:22:07 -0400 ]]

Thanks for the quick reply, Rory.

See the attached, which contains a small test source and some results 
for a few different sites. A couple of sites worked well, but a couple 
do not. Unfortunately for me, my public site is one that does not work. 
(But commons-net-1.3.0 works for all, so I'll be using that for now.)

Let me know if you need more info, I'll try my best to get what you need.

Regards,

Bill


-- 
William Giel, LS
======================
Rocco V. D'Andrea, Inc.
PO Box 549 / Six Neil Lane
Riverside, CT 06460
203-637-1779 (Voice)
203-637-1770 (Fax)
bgiel@rvdi.com
www.rvdi.com

[demime 1.01d removed an attachment of type application/x-zip-compressed which had a name
of timestamp-issue.zip]


> FTPClient listFiles returns incorrect timestamp on freshly uploaded file but corrects
itself after about 15 minutes
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: NET-140
>                 URL: http://issues.apache.org/jira/browse/NET-140
>             Project: Commons Net
>          Issue Type: Bug
>    Affects Versions: 1.4 Final
>         Environment: Windows local client site, Linux remote server site
>            Reporter: Bill Giel
>
> This is an odd one:
> We upload GPS data each hour to a public site using FTPClient. Every 24 hours we check
for files older than 60 days using listFiles and getting the timestamps do decide if we want
to delete older files.
> When we list the files, the most recently uploaded files have a time stamp exactly one
year too old. After about 15 minutes, it seems to correct itself and eventually displays the
correct timestamp.
> During this time while FTPFile.getTimestamp is giving the incorrect timestamp, browsing
the folder with a web browser, a commercial FTP client, or actually checking the file info
in a shell shows the correct timestamp (i.e. does not seem to be a problem on the remote site)
> commons-net-1.4.1 (as well as commons-net-20060901) exhibits this behavior.
> commons-net-1.3.0 works properly
> I did a little investigating, and it seems to happen with every file written to the remote
directory each hour, and the incorrect timestamp will be returned using listFiles for about
15 minutes... and then it corrects itself.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message