It’s strange.
Can you change the route to use camel-http or camel-http4 component to proxy
the request?
In this way we can tell if it is Jetty Client issue.
from("jetty:http://{{smx.host}}:{{smx.rest-proxy-port}}/?matchOnUriPrefix=true";)
.to("http://{{real-server-address}}:{{real-ws-port}}/?bridgeEndpoint=true&throwExceptionOnFailure=false";)
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Thursday, November 7, 2013 at 7:35 PM, berdoni wrote:
> tnx Williem.
>
> I get the same error with enableMultipartFilter=false setting:
> [Body is instance of org.apache.camel.StreamCache]]. Caused by:
> [java.lang.IndexOutOfBoundsException - null]
>
> I get a similar error when I disable stream cache.
> from("../../?matchOnUriPrefix=true&enableMultipartFilter=false&disableStreamCache=true")
>
> The error message is:
> ..Exhausted after delivery attempt: 1 caught:
> org.apache.camel.CamelExchangeException: JettyClient failed cause by: null.
> Exchange[Message: [Body is instance of java.io.InputStream]]. Caused by:
> [java.lang.IndexOutOfBoundsException - null]
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Jetty-proxy-Rest-service-fails-for-file-uploading-tp5742769p5742778.html
> Sent from the Camel - Users mailing list archive at Nabble.com
> (http://Nabble.com).
