[ 
https://issues.apache.org/jira/browse/CAMEL-20965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bartosz Popiela updated CAMEL-20965:
------------------------------------
    Description: InputStreamCache is reset after each step 
(org.apache.camel.impl.engine.CamelInternalProcessor.StreamCachingAdvice#after) 
and if there two threads processing the same InputStreamCache (e.g. Seda), 
there can be a case when one thread invokes InputStreamCache#reset 
(org.apache.camel.support.MessageHelper#resetStreamCache) while another thread 
is converting this InputStreamCache to String 
(org.apache.camel.util.IOHelper#toString(java.io.BufferedReader, long).  (was: 
InputStreamCache is reset after each step 
(org.apache.camel.impl.engine.CamelInternalProcessor.StreamCachingAdvice#after) 
and if there two threads processing the same InputStreamCache (e.g. Seda), 
there can be a case when t one thread can invoke InputStreamCache#reset is 
invoked (org.apache.camel.support.MessageHelper#resetStreamCache) when another 
thread is converting this InputStreamCache to String 
(org.apache.camel.util.IOHelper#toString(java.io.BufferedReader, long).)

> InputStreamCache is not thread-safe
> -----------------------------------
>
>                 Key: CAMEL-20965
>                 URL: https://issues.apache.org/jira/browse/CAMEL-20965
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: Bartosz Popiela
>            Priority: Major
>
> InputStreamCache is reset after each step 
> (org.apache.camel.impl.engine.CamelInternalProcessor.StreamCachingAdvice#after)
>  and if there two threads processing the same InputStreamCache (e.g. Seda), 
> there can be a case when one thread invokes InputStreamCache#reset 
> (org.apache.camel.support.MessageHelper#resetStreamCache) while another 
> thread is converting this InputStreamCache to String 
> (org.apache.camel.util.IOHelper#toString(java.io.BufferedReader, long).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to