>From my investigations, this seems to happen because (assuming a SEDA flow), the SedaQueue run method only catches a MessagingException while performing the routing. Any RuntimeException or Error thrown from an engine in the flow will cause the SedaQueue's thread to silently die.
Michael. -----Original Message----- From: Rob Davies [mailto:[EMAIL PROTECTED] Sent: 21 September 2005 13:40 To: [email protected] Subject: Re: [servicemix-user] Exception thrown in component halts message processing? Hi Matthew, ideally ServiceMix would be able to cope with this. Can you send me a stack trace, or preferably raise a jira issue with a stack trace in so I can handle correctly for Exchange routing ? cheers, Rob On 21 Sep 2005, at 12:50, Matthew Clark wrote: > Quick question - how should the ServiceMix container react if an > unexpected Exception is thrown in a component? > > We have a component that was throwing a > StringIndexOutOfBoundsException. > The result of this was that any further messages sent to this > component > were not being processed. > > Obviously in an ideal situation, we would have no unexpected > exceptions > thrown but is there a way to determine if a component is no longer > responding and/or prevent this behaviour? > > Matthew. > > > > This message has been scanned for viruses. > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, forwarding or otherwise distributing or taking any action in reliance on the contents of this information is strictly prohibited.
