[
https://issues.apache.org/jira/browse/NET-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rory Winston closed NET-140.
----------------------------
Resolution: Fixed
Fix Version/s: 2.0
The only reason I can see that the timestamp will be out of sync for 15 minutes
and then ok is if the FTP server sends a different timestamp for files that
are older than 15 minutes. This will result in the above behaviour.
I have implemented a workaround for this problem - by calling
FTPClient::setDateRollbackPermitted(false), the rollback by 1year should not
occur for these situations.
Any issues, feel free to reopen.
> FTPClient listFiles returns incorrect timestamp on freshly uploaded file but
> corrects itself after about 15 minutes
> -------------------------------------------------------------------------------------------------------------------
>
> Key: NET-140
> URL: https://issues.apache.org/jira/browse/NET-140
> Project: Commons Net
> Issue Type: Bug
> Affects Versions: 1.4
> Environment: Windows local client site, Linux remote server site
> Reporter: Bill Giel
> Fix For: 2.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
