jmx-gateway bundle does not differentiate between failed connection to the
JMXserver versus empty result
--------------------------------------------------------------------------------------------------------
Key: RADMAN-15
URL: http://issues.ops4j.org/jira/browse/RADMAN-15
Project: Pax RadMan
Issue Type: New Feature
Components: BOOTSTRAP
Reporter: Gavin Bong
Assignee: Edward Yakop
Regarding the bundle ( &( groupId=org.ops4j.pax.radman.server.jmx ) (
artifactId=gateway ) ),
the class org.ops4j.pax.radman.jmx.gateway.internal.RadmanServiceImpl does not
differentiate between
a failure connecting to the server & an empty result.
i.e.
public final Set getServices()
{
if( m_radmanService != null )
{
return m_radmanService.getServices();
}
else
{
LOGGER.warn( "RadmanService [" + m_jmxServiceURL + "] is not
initialized." );
return Collections.emptySet();
}
}
>From the RCP client standpoint, it would be better to be able to inform the
>user that the jmx-gateway could not connect to the server
when ( m_radmanService == null ). That way, the user can perform corrective
action e.g. ensure network access is ok, or start the server (if the
server is not running).
In the current implementation, the caller of the getServices() method cannot
DIFFERENTIATE a REAL empty result versus a network connection problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
