DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=37295>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37295 ------- Additional Comments From [EMAIL PROTECTED] 2005-10-31 10:26 ------- This has to be some JVM/network IO quirk. Unless you have any filtering turned on, <copy> just reads in blocks of 8192 bytes and writes it out, using iostreams, breaking the moment that the read fails. It also has to be pretty obscure, as it would have been reported before. 1. try using a drive letter path and not a //machine/path, as that is one difference between your use and Jan's. 2. How far away is the network drive? This feels like network problems. Maybe the issue is that the read() is failing but not reporting a network error, the way it should. We may want to think about reading the length of the file when we start the copy and verifying that at least that many bytes came in, but that will probably break things that copy live resources. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
