Issue in my MightCorrelateSample

Published Tue, Apr 20 2004 11:08 PM

I published last week about how to handle messages that might correlate (see this post). When implementing it, I stumbled upon the issue that although I handled the exception, the messages that failed to correlate show up as suspended in the HAT (twice).

That is a serious problem with this nice solution. In my project we decided that these messages are expected and I wrote a Windows Service, based on a post I found on Darren Jefford's blog, that kills of those messages. Mail me if you're interested in the code, I can send you a copy of the Windows Service.

Although problem solved, I'm now left with the feeling that there has to be a better way to handle messages that might correlate. Any idea's?

by Carlo Poli
Filed under:

Comments

# Carlo Poli said on Tuesday, May 04, 2004 7:55 PM

I'm looking for a windows service to catch suspended messages. Can you e-mail me the sample code of the windows service to deepak@triad.rr.com?

Thanks for your help.

# Carlo Poli said on Tuesday, August 10, 2004 11:41 AM

I urgently need this service, Can you please mail it to me at
kaushik.ruparel@lntinfotech.com

Thanks

# Carlo Poli said on Tuesday, June 28, 2005 9:42 PM

I think you can get around the service by catching
"Microsoft.XLANGs.BaseTypes.PersistenceException"
when sending the Message to the correlating port.

by catching this type you won`t have suspended instances in HAT. But I´d be interested in the service anyway.
kind regards
jive@derjay.de

# Carlo Poli said on Tuesday, June 28, 2005 11:14 PM

damn i forgot to switch to all services in HAT you are right, the routing failure message remains.... no chance to catch them nor to compensate what i tried as well. Did you find any other solution for this problem?