If the file.close takes a lot of time to finish (more than what it would take to write a
whole new file), the server will wait until a new file is opened.
But from what I have seen on my tests TimeCompletion < TimeWrite, i.e. by the time a
new file is required you will already have a new file opened.
what means this condition shouldn't happen under regular circumstances.
That's why I think this is not an issue. It would only happen if the disk was really
slow. (Maybe some other application sharing the disk with JBM, and that would cause delays
anyway).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173353#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...