I'll look at the patches..it could be some network timeout that needs to be set 
higher.

For future reference, here's a link to the msg on the commons-dev mailing list:
http://marc.info/?l=jakarta-commons-dev&m=118180358305021&w=2


Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR  97201

Telephone:      503.224.7496
Cell:           503.997.1367
Fax:            503.222.0185

[EMAIL PROTECTED]

www.comotivsystems.com



-----Original Message-----
From: Isuru Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Thu 6/14/2007 12:05 AM
To: Log4J Developers List
Subject: Issue in fixing 'tailing' in Chainsaw
 
Hi Scott and Pual,

I tried to fix the bug with tailing on VFSLogFilePatternReceiver according
to the method I explained in my previous mail. According to the provided
interface of VFS, I think it is the best way of fixing this problem. So I
implemented it and tested it under different scenarios.
After my new fix, when the log file which is accessed through http (or some
other protocol) receives log events frequently (without time gaps of more
than 10 or 15 seconds), they are loaded on the fly in to Chainsaw and it
works fine. But when new log events are not added to the log file for some
time (more than about 15 seconds), 'rac.getInputStream()' (rac =
RandomAccessContent Object) method call gives an exeption and execution gets
stuck. Even if new log events are added to the log file later, it remains
stuck. But for log files on the local file system, this method works fine. I
sent the 2 patches containing changes to the VFSLogFilePatternReceiver class
in Chainsaw and LogFilePatternReceiver in log4j. Please check it.
I experimented many different ways of overcomming this issue, but it
remains. I think this is a bug in Commons-VFS and I put a mail to their
mailing list and hopefully they will suggest some solution for that.
Sorry for taking too long for this fix due to this unexpected problem with
VFS. While trying to fix this issue completely, I'll start working on my
other tasks as well.

Thanks,
~Isuru

<<winmail.dat>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to