The dispatchToSubscribers is only used for publish/subscribe mode.
You can turn on debug logging to see what happens on the exchange,
but i guess the target component either:
* do not implement MessageExchangeListener
* do not poll the DeliveryChannel for exchanges
Cheers,
Guillaume Nodet
On 6/16/06, KBerthelot <[EMAIL PROTECTED]> wrote:
I'm trying to route a message to a jsr181 component using sendSync and
seda
flow. I've debugged through the ServiceMix code and can see that
DefaultBroker can find the route for the exchange and flow.send()
successfully queues the MessageExchange (with the correct destination
endpoint "echoComponent" set). But then dispatchToSubscribers() doesn't
find any matching subscription endpoints so the exchange is never received
by the destination endpoint and the sendSync silently fails because the
return value from dispatchToSubscribers() is thrown away. I'm assuming
the
problem is that there are no components "subscribed" to the seda queue and
that it could be because of an incorrect configuration , but it's not
apparent exactly where the problem is.
This is the configuratiion for the jsr181 component:
<sm:container id="jbi" useMBeanServer="true" createMBeanServer="true"
embedded="true">
<sm:activationSpecs>
.
.
.
<sm:activationSpec componentName="echoComponent"
service="edgenet:EchoService" endpoint="testService">
<sm:component>
<jsr181:component>
<jsr181:endpoints>
<jsr181:endpoint
pojoClass="
com.edgenet.test.TestEchoService"
service="edgenet:EchoService"
annotations="none"
endpoint="testService"
/>
</jsr181:endpoints>
</jsr181:component>
</sm:component>
</sm:activationSpec>
</sm:activationSpecs>
</sm:container>
--
View this message in context:
http://www.nabble.com/NM-Routing-Problems-t1798899.html#a4902396
Sent from the ServiceMix - User forum at Nabble.com.
