One thing that I'll have to look it is to make sure no confusing
exceptions are reported when something goes wrong during the actual
message post/sending...
It might be a connection timeout actually...You can not control it with
2.0 API though, do the following with WebClient (just to verify if it
makes a difference):
WebClient wc = WebClient.create(address);
wc.type(SOME_MT).accept(SOME_MT);
HttpConduit hc = WebClient.getConfig(wc).getHttpConduit();
hc.getClient().setReceiveTimeout(1000000000L);
hc.getClient().setConnectionTimeout(1000000000L);
Response r = wc.post(byteArray);
if that works then we can discuss how this can be done in the
configuration and also how to optimize at the receiving end.
Sergey
On 25/02/15 18:47, lcasapu wrote:
Sergey, I run your test code ( byte[] theBytes = new byte[]{11, 11}; ) in my
environment, and it appears to work fine. The server gets the bytes, then,
as expected, responds with an error, which is successfully returned to my
client code.
When I revert to posting my 3MB RPM byte[], I still get the error indicated
in my previous post.
This occurs on both CXF 3.0.0 & 3.0.4.
The only logical conclusion is that the array size makes a difference. Are
there any known upload size limitations?
Liviu
--
View this message in context:
http://cxf.547215.n5.nabble.com/Unable-to-upload-file-content-using-CXF-3-0-0-and-Jackson-2-2-0-tp5754611p5754614.html
Sent from the cxf-user mailing list archive at Nabble.com.
