[
http://jira.jboss.com/jira/browse/JBMESSAGING-762?page=all ]
Ovidiu Feodorov closed JBMESSAGING-762.
---------------------------------------
Resolution: Won't Fix
The only place establishLease() is called is Client.setupClientLease(), which is only
called from Client.connect(). Whether connect() fails or not doesn't affect Messaging
failover, which could only kick in over an already established connection.
Clebert, if you find more situations in which Remoting throws raw java.lang.Exceptions,
please open individual JIRA issues and also create test cases that fail in
tests/src/org/jboss/test/thirdparty/remoting
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