The problem has been solved. In fact, the streamCaching works perfectly. The problem was in one of our own processor-classes. I tried to manually send a copy of the exchange to both multicast-endpoints, so that i did not require the multicast()-function any more. But the problem stayed, so i became suspicious and checked our processor-implementation. First i thought it would get an empty stream, but thats not the point. Finally, the problem is that being invoked for the second time, the processor runtime object starts in a different state than in the first time.
Sorry for stealing your time... -- View this message in context: http://www.nabble.com/StreamCachingInterceptor-question-tp20561886s22882p20597543.html Sent from the Camel - Users mailing list archive at Nabble.com.
