Hello,
I'm using camel routes for processing and I thought that the process is
synchronous, unless parallel processing is specified. I have a processor
that unmarshalls from xml strings and I noticed the following in the
logging:
DefaultMessageListenerContainer-2 | UnmarshallerProcessor |
rocessor.UnmarshallerProcessor 33 | Accessed by thread:
DefaultMessageListenerContainer-2
DefaultMessageListenerContainer-10 | UnmarshallerProcessor |
rocessor.UnmarshallerProcessor 33 | Accessed by thread:
DefaultMessageListenerContainer-10
DefaultMessageListenerContainer-4 | UnmarshallerProcessor |
rocessor.UnmarshallerProcessor 33 | Accessed by thread:
DefaultMessageListenerContainer-4
DefaultMessageListenerContainer-3 | UnmarshallerProcessor |
rocessor.UnmarshallerProcessor 33 | Accessed by thread:
DefaultMessageListenerContainer-3
DefaultMessageListenerContainer-9 | UnmarshallerProcessor |
rocessor.UnmarshallerProcessor 33 | Accessed by thread:
DefaultMessageListenerContainer-9
DefaultMessageListenerContainer-7 | UnmarshallerProcessor |
rocessor.UnmarshallerProcessor 33 | Accessed by thread:
DefaultMessageListenerContainer-7
DefaultMessageListenerContainer-5 | UnmarshallerProcessor |
rocessor.UnmarshallerProcessor 33 | Accessed by thread:
DefaultMessageListenerContainer-5
So, if I'm not mistaken, the process method of the UnmarshallerProcessor is
called by different threads and it could lead to serious synchronization
issues if I don't use a lock. Is this correct?
Route without parallel processing explicitly enabled:
from(DIRECT_INPUT)
.process(unmarshallerProcessor)
.to(getOutputEndpoint());
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/Synchronizing-camel-processors-tp5735185.html
Sent from the Camel - Users mailing list archive at Nabble.com.
