search

TheProjecter / sardine

Automatically exported from code.google.com/p/sardine
0 stars 0 forks source link

PUT method will not work with Streams #104

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
"void put(String url, InputStream dataStream)" for eny files, even very small 
ones.

What is the expected output? What do you see instead?
WebDAV copy of file, instead I get this exception:
Caused by: com.googlecode.sardine.impl.SardineException: Unexpected response at 
com.googlecode.sardine.impl.handler.
ValidatingResponseHandler.validateResponse(ValidatingResponseHandler.java:49)
    at com.googlecode.sardine.impl.handler.VoidResponseHandler
.handleResponse(VoidResponseHandler.java:35)
    at com.googlecode.sardin.....

What version of the product are you using?
284

On what operating system?
Linux/Win7

What webdav server are you hitting?
Apache Slide (last version)

What is in the server error logs?
org.apache.slide.common.ServiceAccessException: Service 
org.apache.slide.store.impl.rdbms.J2EEStore@58c858c8 access error : Async 
operation timed out 

If I use the sardine method
"void put(String url, byte[] data)"

no problem occurs. BUT, then I run into OutOfMemory Exception in my system 
because the whole file is in memory. And I NEED TO COPY big files (e.g. 500MB).

I've followed the other issues, e.g. setting up an "exists" before soing the 
copy. But nothing helped! If I copy the big file through a Microsoft Internet 
Explorer (built in WebDAV Client) everything works. Even using an Apache Slide 
WebDAV Client (command tool) works fine! BUT, I can't adopt the Apache Slide 
Client, because all of its dependencies are so old which would affect my whole 
system!

Original issue reported on code.google.com by maik.mra...@gmail.com on 28 Jul 2011 at 3:07

GoogleCodeExporter commented 9 years ago 
Can you please include the full stack trace?

Original comment by latch...@gmail.com on 28 Jul 2011 at 5:03

GoogleCodeExporter commented 9 years ago 
Post the message in the exception thrown which will include the HTTP status 
response from the server. Or set up logging of `org.apache.http.headers` with 
Log4j to debug level.

Original comment by dkocher@sudo.ch on 28 Jul 2011 at 7:14

GoogleCodeExporter commented 9 years ago 
Closing due to lack of feedback.

Original comment by dkocher@sudo.ch on 7 Aug 2011 at 4:43