camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-782) Tracer incorrectly treats messages with InputStream as body
Date Wed, 06 Aug 2008 04:15:52 GMT


Claus Ibsen commented on CAMEL-782:

Ah good catch. The logger could have the same problem as well.

I remember there is something with streamcache that might can help out here. I don't have
the time to dig into it yet.

A workaround is to disable logging of the body in the tracer. There are options for this in
the formatter:

> Tracer incorrectly treats messages with InputStream as body
> -----------------------------------------------------------
>                 Key: CAMEL-782
>                 URL:
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: Genadii Ganebnyi
> Suppose we have the following flow:
>  from("activemq:vasea")
>   .to("cxf:bean:serviceEndpoint?dataFormat=MESSAGE")
>     .unmarshal().string()
>   .to("activemq:petea");
> In this flow cxf:bean:serviceEndpoint returns ByteArrayInputStream as body. Under normal
conditions everything works fine: WS output gets to the queue.
> But if we add:
> getContext().addInterceptStrategy(new Tracer());
> Queue starts receiving empty messages. After digging in the code I found out that tracer
reads input stream in order to display body, but not resets it. Thus when message reaches
unmarshaller, nothing could be read from the stream.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message