[jira] [Created] (CAMEL-10568) SftpChangedExclusiveReadLockStrategy setting new last modified time as negative

["Adam Campbell (JIRA)" <ji...@apache.org>]

Adam Campbell created CAMEL-10568:
-------------------------------------

             Summary: SftpChangedExclusiveReadLockStrategy setting new last modified time as negative
                 Key: CAMEL-10568
                 URL: https://issues.apache.org/jira/browse/CAMEL-10568
             Project: Camel
          Issue Type: Bug
          Components: camel-sftp
    Affects Versions: 2.18.0
            Reporter: Adam Campbell


It looks like CAMEL-9820 has not resolved SFTP readLockMinAge functionality.

When I run the latest version, I get a new last modified time as negative. I think this is because both types are int so it is performing the calculation as an int and then converting it to long.

It should work if this line:

newLastModified = f.getAttrs().getMTime() * 1000;

Is changed to:

newLastModified = f.getAttrs().getMTime() * 1000L;


TRACE o.a.c.c.f.r.s.SftpChangedExclusiveReadLockStrategy - List files outgoing/Promo/dev/test.dat found 1 files
TRACE o.a.c.c.f.r.s.SftpChangedExclusiveReadLockStrategy - Previous last modified: -9223372036854775808, new last modified: -616826120
TRACE o.a.c.c.f.r.s.SftpChangedExclusiveReadLockStrategy - Previous length: -9223372036854775808, new length: 12921172
TRACE o.a.c.c.f.r.s.SftpChangedExclusiveReadLockStrategy - New older than threshold: 1481147995902
TRACE o.a.c.c.f.r.s.SftpChangedExclusiveReadLockStrategy - Read lock acquired.



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