Silvia,
The servicemix-bean component uses a thread pool to handle multiple
messages concurrently. There's not really anything special you need to
do, but you should however take care to write your onMessageExchange
method in a thread-safe way. Btw, I guess you're using a JMS and Bean
SU, right?
If you have any more problems with this, could you post the code from
you servicemix-bean component. Another possibility to troubleshoot this
is by enabling DEBUG logging and looking at the MessageExchanges (more
particularly at the MEP and the status code) to figure out where
messages get lost.
Regards,
Gert
silvia_magrelli wrote:
Hi,
I have implemented my publish\subscribe with bcs and bean ses
and 1 topic. I have to realize many to many comunication.
If I realize one to many comunication (1 publisher and 3 subscribers(one of the subscriber is the publisher itself)) all works well.
Instead if I use many to many with all the three component that
i have are publisher and subscriber at the same time then some
message get lost.
I wonder that the reason is that the call to onMessageExchange in my bean that found it busy doesn't
retry for a second time, there isn't buffering of
such method's invocations or there isn't a new thread that
treat the message receiving.
Did I understand well?
What methods and classes should I have to use in servicemix
to not loose messages and treat them all in my java-bean components ?
(I'm using servicemix 3.2.1)
Please help me!
Thank You in advance for your help!
greetings,
silvia
