tag:blogger.com,1999:blog-4148344860241019504.post3289344814541612544..comments2024-03-26T18:47:12.971+05:30Comments on TechFindings...by Maheshkumar Tiwari: Routing Failure ReportMaheshkumar Tiwarihttp://www.blogger.com/profile/14535330323990019022noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4148344860241019504.post-52416492619909358732017-04-05T15:37:27.281+05:302017-04-05T15:37:27.281+05:30Yes, that's an option. But here, the source ap...Yes, that's an option. But here, the source application doesn't want to receive exception (exception has to be reported to support team) and only functional response is expected by source.Maheshkumar Tiwarihttps://www.blogger.com/profile/14535330323990019022noreply@blogger.comtag:blogger.com,1999:blog-4148344860241019504.post-65307748513111928262017-04-05T15:21:03.093+05:302017-04-05T15:21:03.093+05:30What you can do is handle the exception as you are...What you can do is handle the exception as you are doing currently, create a message with meaningful error information and send back to the receive port, i believe that is req-res port. In that case you will not get this kind of routing failure further.<br /><br />Thanks<br />PriyankarAnonymousnoreply@blogger.com