Hello,
I am not able to test this at the moment but what happens if you change the
first "from" to from("jetty:" + URI).log("${body} and ${headers}".to("")
In the case of the empty messages, does the log statement also show that
the body being empty?
You can also include debug level logs in your test to further break things
down to see if there is something obvious going on. To do that include the
variables:
private boolean debugBeforeMethodCalled:
private boolean debugAfterMethodCalled:
Include the methods:
@Override
protected void debugBefore(Exchange exchange,
org.apache.camel.Processor processor, ProcessorDefinition<?>
definition, String id, String label) {
log.info("Before " + definition + " with body " + exchange.getIn().getBody());
debugBeforeMethodCalled = true;
}
@Override
protected void debugAfter(Exchange exchange,
org.apache.camel.Processor processor, ProcessorDefinition<?>
definition, String id, String label, long timeTaken) {
log.info("After " + definition + " with body " + exchange.getIn().getBody());
debugAfterMethodCalled = true;
}
Best
Souciance
On Tue, Jun 14, 2016 at 1:44 PM, Bjørn Ellingsen-2 [via Camel] <
ml-node+s465427n5784020...@n5.nabble.com> wrote:
> Hi, I get sporadic cases of no body when having a client sending small
> JSON messages over http, and a jetty endpoint receiving them, and a
> short route with a vm endpoint and a bean. Stream-caching is enabled.
> The issue only appears when MEP is InOnly. A simple test case to
> reproduce the issue is attached, you might have to adjust (increase) the
> message count if test executes without failure.
>
> Enabling trace logging on org.apache.camel, there is only one log
> statement I noticed to differ when message came through vs. was lost:
>
> 2016-06-14 12:50:49.441 [TRACE] [MethodInfo] []: Parameter #0 evaluated
> as:
> {"key1":"value1","key2":"value2","key3":"value3","key4":"value4","key5":"value5"}
>
> type:
>
> vs.:
>
> 2016-06-14 12:50:49.547 [TRACE] [MethodInfo] []: Parameter #0 evaluated
> as: type:
>
> The number of lost messages - or empty bodied messages - when running
> this test case is in the range 5-50 (out of 800). I have avoided the
> issue for now by converting the body from stream to string, but I would
> really like to know if I'm using the API wrong or if there is a bug
> hidden somewhere. Any help appreciated.
>
> Versions etc:
> Camel: 2.17.1
> JDK: 1.8.0_77
> Jetty: 9.2.15 (also tried 9.1.6)
> OS: Fedora + RHEL
> Same result if using other client than camel-http
>
> Regards,
> Bjørn E.
>
> *CamelStreamConverterTest.java* (1K) Download Attachment
> <http://camel.465427.n5.nabble.com/attachment/5784020/0/CamelStreamConverterTest.java>
> *log4j2-test.xml* (476 bytes) Download Attachment
> <http://camel.465427.n5.nabble.com/attachment/5784020/1/log4j2-test.xml>
> *pom.xml* (1K) Download Attachment
> <http://camel.465427.n5.nabble.com/attachment/5784020/2/pom.xml>
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/Lost-messages-when-streaming-with-Jetty-tp5784020.html
> To start a new topic under Camel - Users, email
> ml-node+s465427n465428...@n5.nabble.com
> To unsubscribe from Camel - Users, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View this message in context:
http://camel.465427.n5.nabble.com/Lost-messages-when-streaming-with-Jetty-tp5784020p5784023.html
Sent from the Camel - Users mailing list archive at Nabble.com.
