[ http://jira.jboss.com/jira/browse/JBREM-17?page=history ]
Tom Elrod closed JBREM-17:
---------------------------
Resolution: Done
All transports (rmi, socket, and http) now throw the CannotConnectException in
their client invokers if they can not make a connection to their server
invokers.
> Add CannotConnectException to all transports
> --------------------------------------------
>
> Key: JBREM-17
> URL: http://jira.jboss.com/jira/browse/JBREM-17
> Project: JBoss Remoting
> Type: Task
> Components: transport
> Versions: 1.0.1 alpha
> Reporter: Tom Elrod
> Assignee: Tom Elrod
> Priority: Critical
> Fix For: 1.0.1 beta
>
>
> Add a CannotConnectException to Remoting transports as well as catch
> ConnectException and throw CannotConnectException instead.
> Bill has already done this for the socket invoker on 4.0 branch.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
