Niklas, Thanks for the info about the DEBUG option. I was using this option. The problem with the mget that I was facing has been resolved. I was not correctly returning the response for an NLST and that was causing the problem.
Thank you, Ajith -----Original Message----- From: [EMAIL PROTECTED] on behalf of Niklas Gustavsson Sent: Wed 2/20/2008 9:15 AM To: [email protected] Subject: Re: Problem with mget DEBUG is the lowest level that we log at (there is also TRACE but we don't use it). The following in log4j.properties should give you the output into a file: log4j.rootLogger=DEBUG, logfile log4j.appender.logfile=org.apache.log4j.FileAppender log4j.appender.logfile.File=c:/tmp/ftpserver.log log4j.appender.logfile.layout=org.apache.log4j.PatternLayout log4j.appender.logfile.layout.ConversionPattern=%d %p [%c] - %m%n /niklas On Feb 18, 2008 11:13 PM, Janardhanan, Ajith (AJANARDH) <[EMAIL PROTECTED]> wrote: > Hi, > I am running into another problem with Apache ftp server. I have an > embedded ftpserver in my code and when I try to do an mget *.* from the > ftp client(the ftp client in windows and solaris), looks like the server > is hanging and dont send any reponse. > I did some debugging and saw that the FTP commands sent are TYPE A and > NLST. I see that NLST *.* is sent and no RETR command is sent > > Attaching the log file. Looking at the log file, is there another level > of DEBUG option possible? I have set log4j.rootCategory=DEBUG in my > log4j.properties file. > > Appreciate some help in this. > > Regards > Ajith > > >
