[CAMEL-20965] InputStreamCache is not thread-safe

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 4.4.3, 4.6.0
• Fix Version/s: 4.7.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Bartosz Popiela
• Created: 10/Jul/24 14:26
• Updated: 17/Jul/24 01:42
• Resolved: 17/Jul/24 01:42

Description

InputStreamCache is reset after each step (org.apache.camel.impl.engine.CamelInternalProcessor.StreamCachingAdvice#after), and if there are two threads processing the same InputStreamCache (e.g. Seda), there may be a case where one thread invokes InputStreamCache#reset (org.apache.camel.support.MessageHelper#resetStreamCache) while another thread converts this InputStreamCache to String (org.apache.camel.util.IOHelper#toString(java.io.BufferedReader, long). It leads to java.io.ByteArrayInputStream#pos being reset and the target String having duplicate entries.

Issue Links

• relates to: CAMEL-20866 SEDA with exchangepattern InOnly gives sometimes multiple responses
• links to: Test Case