Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.0.1
-
Fix Version/s: 2.1.0
-
Labels:None
-
Number of attachments :
Description
The standard JMS mechanism to detect dead connections is to register a javax.jms.ExceptionListener on a JMS connection. BTM's JMS pool should do this and close the offending connection when the proper exception is received by the listener.
This will require testing against a large et of JMS servers to make sure this feature can work reliably.
When ExceptionListener.onException() any kind of JMS exception can be passed to the method, it's not possible to know if the problem has to do with the connection being invalid or not with the exception type.
The official way to discriminate between error types is to check JMSException.getErrorCode(). Unfortunately this code is vendor-specific, there's no standard error code and some JMS servers don't even bother to fill it in.
This feature basically is useless to detect JMS connection problems.