On 2012-2-16, at 下午3:25, Naveen wrote:
Hi,
saxon endpoint isn't available anymore
Means it was available at start and later removed?
Do you mean it works previously but stop working after 3 days?
No, I don't know if it was available earlier, assumed so as started
seeing
this log after 3 days of servicemix start -
2012-02-06 11:26:33,745 | WARN |
pool-flow.seda.gep-event-receiver-se-thread-25 |
DefaultBroker |
rvicemix.jbi.nmr.DefaultBroker 344 | ServiceName
({urn:ofas:sql:converter}ofas2SQL) specified for routing, but can't
find it
registered
This means the Service urn:ofas:sql:converter}ofas2SQL isn't in the
container when deliver message, it could be caused that this service
never up or it was up but somehow it's down when deliver message. Are
you sure the saxon endpoint is started successfully? Did you ever send
message to saxon endpoint successfully?
Freeman
My understanding is that all endpoints will be started and made
available
when SA is deployed successfully when servicemix comes up. If that
is true
then what is justification for this error after 3 days of servicemix
start?
Is it a possibility that Saxon component was removed/undeployed
later but
even in that case SU targeting this component also should throw some
exception.
Regards,
Naveen
--
View this message in context:
http://servicemix.396122.n5.nabble.com/Could-not-find-route-for-exchange-Saxon-tp5488601p5488738.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
---------------------------------------------
Freeman Fang
FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
