anonymous wrote : To clarify: | | You're saying the move to next file would currently block until the old file could be closed? | I aways have one file opened. There is one wait. The only possibility waits on nextFile is if .close is taking more time than what it takes to write data to a file. This would be a lack of resources problem from the hardware, and I can't do any magics. If the system/HD is slow because of overuse.. it is slow.. what can I do? anonymous wrote : Yes it's unlikely, but it's possible and therefore is an issue. What can I do if the hardware is not answering properly? There is nothing I can do here. Opening several files would only worsen the situation on the hardware. anonymous wrote : Anything that might happen, however unlikely we must handle, rather than just barf. We won't barf... we would wait until the openedFileCache was restablished. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173386#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...