Bug #3209
closedecogrid SearchRegistryAction error when disconnected from network
0%
Description
About 30 seconds after starting kepler with no network connection, a long error
message is displayed, starting with:
[java] ERROR (org.ecoinformatics.seek.ecogrid.SearchRegistryAction:queryRegistryRewriteConfig:210) problem looking up registry entries using endpoint: http://knb.ecoinformatics.org/registry/services/RegistryServiceMost likely caused by the fix for 3124.
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3124
Updated by ben leinfelder about 16 years ago
sounds like some error catching is in order. should there be an alert using MessageHandler (attack of the pop up window!) or should it just log the error and move on with life?
Updated by Daniel Crawl about 16 years ago
I'd say show an alert when something is trying to use a data source, e.g. the ecogrid actor. Otherwise, ignore it.
Updated by ben leinfelder about 16 years ago
added messagehandler error reporting when the services registry is not available.
if, on start up, there is an error accessing the registry, an alert is shown (in kepler gui mode, at least).
Updated by Daniel Crawl about 16 years ago
I'm reopening this since the error window now occurs regardless of any data sources actually being used (either the Data tab or ecogrid actors).
This seems low priority so could be re-targeted to 1.1.
Updated by Jing Tao about 16 years ago
The short term solution is just removing the error message. Kepler will keep silent if it couldn't connect to the registry.
The long term solution is assigned to bug 3228.
Updated by Jing Tao about 16 years ago
Remove the error message panel and decrease debug level from error to warn in src/org/ecoinformatics/seek/ecogrid/SearchRegistryAction.java class. Now if kepler couldn't contact registry because of network disconnection and it will keep silence.