You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2016/06/28 06:47:57 UTC

[jira] [Created] (CAMEL-10096) Camel tracer with stream caching should tracer after stream cache has been setup

Claus Ibsen created CAMEL-10096:
-----------------------------------

             Summary: Camel tracer with stream caching should tracer after stream cache has been setup
                 Key: CAMEL-10096
                 URL: https://issues.apache.org/jira/browse/CAMEL-10096
             Project: Camel
          Issue Type: Improvement
          Components: camel-core
    Affects Versions: 2.17.1
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
             Fix For: 2.17.3, 2.18.0


When using tracer then it may run before stream caching gets kicked-in, which means the tracer may read the input stream causing the stream to not be re-readable by the stream caching, and therefore cause it to be empty.

This only happens if you turn on stream cache bodies on the tracer, which is off by default. And if the input message is stream based that is no re-readable by itself.

We should ensure the stream caching advice is run first so its applied before any tracer and other stuff going on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)