[ http://issues.apache.org/jira/brows...23589
15 ]

Julien Vermillard commented on DIRMINA-135:
-------------------------------------------

It's how I do actualy I got a Thread for trying to connect the Connector, I 
tried to implement that in a filter and effectivly it's not really clever, I
 think my ReconnectionFilter will just try to reconnect disconnected connect
ors. This issue can be clos
ed.

> exception during a connector.connect() aren't caught by filters
> ---------------------------------------------------------------
>
>          Key: DIRMINA-135
>          URL: http://issues.apache.org/jira/browse/DIRMINA-135
>      Project: Directory MINA
>         Type: Bug
>     Versions: 0.8.1, 0.8, 0.8.2
>  Environment: MINA 0.8 and a SocketConnector
>     Reporter: Julien Vermillard
>     Priority: Minor

>
> I try to do a reconnection filter, automaticly connecting and reconnecting
 a connector until it works.
> if theinitial connector.connect(...) fail, and exception is thrown, but it
's not caught by IoFilter chain. It's not really a bug I think but I added a
 simple fix :
> in SocketConnector class in the connect method :
>     public IoSession connect( SocketAddress address, SocketAddress localAd
dress,
>                               int timeout, IoHandler handler ) throws IOEx
ception
> I changed :
> ....
>         if( request.exception != null )
>         {
>             ExceptionUtil.throwException( request.exception );
>         }
> ....
> into
> ....
>         if( request.exception != null )
>         {
>        	    filters.exceptionCaught(null,request.exception );
>             ExceptionUtil.throwException( request.exception );
>         }
> ....
> and now my filters get the exception normaly, perhaps it's an idea to add it to MI
NA 0.8 ?

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secur...nistrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]