in that some commands are never logged, or just on
some sessions?
Can anyone think of a way that the file could be transfered without our
ftplet being called? Are there default ftplets that might have told it to
skip further processing before it got to ours?
No, there are no default Ftplets
, but its become
frustrating that it happens rarely and there is nothing logged that
indicates what might be going on.
Can anyone think of a way that the file could be transfered without our
ftplet being called? Are there default ftplets that might have told it
to
skip further processing
On Wed, Jun 8, 2011 at 5:44 AM, Niklas Gustavsson nik...@protocol7.comwrote:
Which exact log statement is it that you were expecting? From
FtpLoggingFilter?
What logging provider are you using? Assuming this is a race
condition, it could be both in FtpServer, slf4j and the logging
On Wed, Jun 8, 2011 at 12:55 PM, Allen Firstenberg
prof...@addventure.com wrote:
The logging in this case isn't code level logging, it is command/transfer
logging. It is an ftplet that can be configured to log various attributes
from an FtpSession, FtpRequest, and/or FtpReply. It is intended
Hello Allen,
I would need some more info for this, e.g.,
1) Are the clients using FTP or FTPS?
2) Are they using a 'publicly available' FTP client? which one?
3) Is it possible that you're capturing some exceptions silently?
If I understand you correctly, FTPServer itself has logging
On Wed, Jun 8, 2011 at 7:10 AM, Niklas Gustavsson nik...@protocol7.comwrote:
Sorry, I forgot the basic problem you described. I've reviewed our
code, and fail to find a way that Ftplet.beforeCommand() would not be
called. Ftplet.afterCommand() could of course we skipped if
beforeCommand
the transfer appears to have succeeded. There are numerous errors
sent to stdout about pipes being closed on either the command or data
channel, so we can't trace them to a specific instance.
Can anyone think of a way that the file could be transfered without our
ftplet being called
be transfered without our
ftplet being called? Are there default ftplets that might have told it
to
skip further processing before it got to ours?
Any thoughts about this, or how to track down the problem on a production
server, would be greatly appreciated.
Thanks!
Allen
