Rajith,
I think the point here is how you differentiate exceptions which should be
handled at the connection level and those which should be handled at the
session level (or even somewhere down the line).
Another concern in this case is the use of failover mutext as per [1].
[1] -
Here I am referring to Session level exceptions, not connection
level exceptions.
I should have made this more explicit with a title like JMS Error
handling at the session level..
For connection level exceptions (IO errors and AMQP connection
exceptions) we always notify through connection
Posting it under a modified subject to highlight the area I am trying
to focus on.
Currently we notify a Session level exception (Execution exception in
0-10 speak) in two different ways (in most cases).
1. We throw a direct exception in the form of a JMS exception
2. We notify via the connection
Folks,
I am trying to tidy up the error handling code in the JMS client and
is soliciting ideas and feedback.
I also have rough proposal outlined below.
Please feel free to make suggestions/improvements for the following
solution or any alternative ideas that you might think maybe better.
