[
http://jira.jboss.com/jira/browse/JBMESSAGING-762?page=comments#action_12... ]
Ovidiu Feodorov commented on JBMESSAGING-762:
---------------------------------------------
According their documentation, they should throw
org.jboss.remoting.CannotConnectException
/**
* This exception is generated when the remoting layer cannot connect to the remote
server
* It means that the client cannot send the request to the server.
* Clustering layers can rely this exception to failover.
*/
JBossRemoting throws java.lang.Exception in certain cases
---------------------------------------------------------
Key: JBMESSAGING-762
URL:
http://jira.jboss.com/jira/browse/JBMESSAGING-762
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.Beta1
Reporter: Clebert Suconic
Assigned To: Ovidiu Feodorov
Fix For: 1.2.0.Beta2
Places where remoting can't connect to a server such as establishLease are throwing
java.lang.Exception("textual messages").
It's impossible to treat those events on Interceptors.
There are already testcases failing because of these things... so I don't know if we
should require a thirdparty test for this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira