Using -Dapache.nntp.debug=true was my first aproach. But what I got was just an output like S: -1 :( this is because in the implementation of PrintWriter in NNTPHandler.handleConnection() only has a debug hook in println(), but does not overwrite print(). So I decided to assemble the line using StringBuffer rather than overwrite print() and buffer the data just for debugging purposes.
So using this solution will give full usable output whenever -Dapache.nntp.debug=true has to be used next. I also checked that there are no further occurences of PrintWriter.print() calls which could produce missing debug data. Christian >> I don't think prt.print(..) to StringBuffer makes a >> difference. PrintWriter will buffer till println is called and it seems a >> bit cleaner. >> >> To debug NNTP protocol, it is best to change runscript to have system >> property -Dapache.nntp.debug=true. Client and Server communication for >> nntp will show up in the log file with prefix 'C: ' and 'S: '. This >> should help identify protocol problems. Helped me a lot. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
