Menu
▾
▴
[Smartfrog-checkins] [Smartfrog.org-JIRA] Commented: (SFOS-1079) sfPing output could be improved
|
From: Steve L. (JIRA) <ji...@sm...> - 2009-01-23 20:04:05
|
[ http://jira.smartfrog.org/jira/browse/SFOS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11471#action_11471 ]
Steve Loughran commented on SFOS-1079:
--------------------------------------
the problem here is that the reg variable is an instance of Registry, created via LocateRegistry.getRegistry(host, port);, and it is just a proxy of (address,port). There is no attempt to reach the host/port until the RMI call is made, at which point you are at the mercy of RMI and its errors.
I propose that for the ping command, we start by trying to open a tcp connection to the port, catching early instances of
NoRouteToHost: network problems, laptop has moved
hostname doesnt resolve
port connection refused
> sfPing output could be improved
> -------------------------------
>
> Key: SFOS-1079
> URL: http://jira.smartfrog.org/jira/browse/SFOS-1079
> Project: SmartFrog
> Issue Type: New Feature
> Components: .sfCore
> Affects Versions: 3.17.004
> Reporter: Steve Loughran
> Assignee: Julio Guijarro
> Priority: Minor
>
> When sfPing fails it could be more helpful
> 2009/01/23 17:32:28:483 GMT [WARN ][main] SFCORE_LOG - SmartFrog security is NOT active
> - FAILED when trying PING of '-v', host:192.168.1.6
> Result:
> * Exception: 'Unable to connect to sfDaemon on: 192.168.1.6.
> Reason: sfDaemon may not be running on 192.168.1.6java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
> java.net.ConnectException: Connection refused'
> 1. Prettier layout
> 2. Better stack trace (how?)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.smartfrog.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|