You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by rbohn <rb...@versatile.com> on 2007/12/13 22:02:25 UTC
Guidelines for handling situations where target service hasn't been
registered yet
I fully expect in an ESB world for endpoints to activate in an unpredictable
order. One particular example that I'm interested in is when one endpoint
sends a messages to another endpoint that hasn't activated yet. What are
some guidelines for handling this situation? I was thinking just to retry x
number of times and then fail if still getting an error. Are there any
other suggestions?
--
View this message in context: http://www.nabble.com/Guidelines-for-handling-situations-where-target-service-hasn%27t-been-registered-yet-tp14324744s12049p14324744.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Guidelines for handling situations where target service hasn't been registered yet
Posted by Bruce Snyder <br...@gmail.com>.
On Dec 13, 2007 2:02 PM, rbohn <rb...@versatile.com> wrote:
>
> I fully expect in an ESB world for endpoints to activate in an unpredictable
> order. One particular example that I'm interested in is when one endpoint
> sends a messages to another endpoint that hasn't activated yet. What are
> some guidelines for handling this situation? I was thinking just to retry x
> number of times and then fail if still getting an error. Are there any
> other suggestions?
How exactly are you sending the messages? Please provide details.
Bruce
--
perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/