Is there a reason, why this patch has not yet made it to the build?
Any server side application using VFS currently may face a hung socket connection because of this issue.
We've been seeing this issue on one of our production servers (where a faulty router sometimes creates this condition ). The system should however be able to recover from this error, which it currently does not, and hangs on waiting indefinitely (till a server restart).
The commons.net already provides the ability to configure socket timeouts ( I believe since commons.net 1.5) as is indicated in the patch by Reetu.
Please suggest a timeline for this patch being rolled out in a VFS build.