If you use ColdFusion Builder and if you use tailview, this post is for you! Tail View is a great functionality in ColdFusion builder that allows you to tail the contents of any log file in real time. It is a great productivity feature that saves you from opening the log file and continuously reloading it.
TailView in ColdFusion Builder keeps watching the file for any modification and if there is any, it updates the view with the latest content. That causes a race condition between the tail view process which is trying to read the file and the server process that is writing to the same file. Generally, in such race conditions, the preference is almost always given to the reader. If there is any read operation (and there can be multiple simultaneous reads) in progress, write operation waits.
Somehow this race condition is not very much visible when the server is running from console. However, when the server is running as a service, this race condition becomes so severe that the server becomes almost unresponsive. The jrunsvc.exe process just hogs up all the CPU cycles and the server becomes nearly dead.
A simple way to fix this is to increase the period at which the tail view checks for a change in the file content. Thankfully ColdFusionBuilder provides a preference to do that.
Go to Windows > Preference > HTML >TailView and change the value of “Read Timeout” from 100 to 1000 or any other suitable higher value. This will give enough time to server threads to write contents to the log file.

#1 by Craig Kaminsky on May 10th, 2010
| Quote
Thanks for the tip … Very helpful!
#2 by Adam Cameron on May 10th, 2010
| Quote
The jrunsvc process, or the jrun process?
My understanding (which is not comprehensive, and based on reading people’s blog entries, spiced with a bit of personal observation) is that all the jrunsvc process is supposed to do is to wrap the jrun app in something that can be called as a service, and then keep an eye on it to make sure it’s running (ie: if you kill the jrun process, jrunsvc will start it again).
Am I understanding things wrong?
–
Adam
#3 by Rupesh Kumar on May 10th, 2010
| Quote
@Adam, Your understanding is absolutely correct. However, it does its own extra bit to redirect the output stream and error stream of JRun process to log files.
#4 by Adam Cameron on May 10th, 2010
| Quote
Gotcha, makes sense. Cheers.
–
Adam
#5 by Raymond Camden on May 13th, 2010
| Quote
Dumb question – if the tailview is not visible, is it still “working” ?
#6 by Success on June 8th, 2010
| Quote
Hello from Vyatka River!!! Thank you for information! Itґs a good idea for next full revision…
))
Write more!!!
#7 by Valerie on May 11th, 2011
| Quote
Thanks for the easy fix — much appreciated!
#8 by Sam Orchard on May 13th, 2011
| Quote
Had no idea this even affected server performance. Thanks for letting me know (and how to fix it!)
#9 by Morris B. on May 14th, 2011
| Quote
Once again, thanks for the help!
#10 by Yasmin on May 17th, 2011
| Quote
I didn’t realize Tail View was such a processor hog — glad I came across this post.
#11 by debbiep on May 19th, 2011
| Quote
thats a really good easy fix for this problem. thanks
#12 by oceanside carpet cleaning on May 20th, 2011
| Quote
I’ve found the this article to be extremely informative. I’ll have to bookmark your site so I can pay a visit to from time to time.
#13 by Ben W. on May 23rd, 2011
| Quote
I wish I read this post weeks ago — it did make a noticeable difference.
#14 by Marry @ Invitation maker on May 25th, 2011
| Quote
Thank you so much for this tip – I had problems with my server and this was the cause.
#15 by Christine Arkin on May 27th, 2011
| Quote
Ah, you always just need to know where to look… I was searching for that preference. Hiding in plain sight.
#16 by Quinn on May 30th, 2011
| Quote
I was wondering why my server seemed sluggish lately — glad there was a simple fix.
#17 by Kerry Enser on August 26th, 2011
| Quote
I had actually stopped using TailView until I learned this trick. I’m glad I’m able to use it again without issue.
#18 by Katie on September 12th, 2011
| Quote
Thanks for the simple fix. It has helped speed things up again.
#19 by cupola on September 21st, 2011
| Quote
Tail view has been a problem of mine for some time now. Simple once you figure it out
#20 by Mike on October 2nd, 2011
| Quote
wow.. its a lot easier when you have that simple fix.. thank you
#21 by PaUL on October 2nd, 2011
| Quote
Thank you for the fix to this issue.. helped a lot
#22 by Lindsay on October 3rd, 2011
| Quote
Thanks for the fix.. took me awhile to find it, but worth the search
#23 by Tom on October 4th, 2011
| Quote
This is so great.. helped a lot
#24 by Kathy on October 4th, 2011
| Quote
this really was helpful.. a few things on your site have helped me out.. thank you
#25 by Lionel on October 7th, 2011
| Quote
great work on this site.. really a pleasure to read
#26 by Quan on October 8th, 2011
| Quote
“That causes a race condition between the tail view process which is trying to read the file and the server process that is writing to the same file” – thanks for including this explanation.. the problem was baffling to me