You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Viet Hung Nguyen (JIRA)" <ji...@apache.org> on 2008/05/16 06:30:56 UTC
[jira] Created: (GERONIMO-4021) monitoring console takes too long
to recognize that a server is offline
monitoring console takes too long to recognize that a server is offline
-----------------------------------------------------------------------
Key: GERONIMO-4021
URL: https://issues.apache.org/jira/browse/GERONIMO-4021
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: monitoring
Reporter: Viet Hung Nguyen
Assignee: Viet Hung Nguyen
Fix For: 2.2
Whenever the monitoring plugin attempts to monitor a server that is offline/doesn't exist, it takes way too long to load the page. We need to reduce this timeout period.
I suggest that we add a parameter for the admin to set as the "timeout period" somewhere in the portlet. By default, we can choose to have this timeout parameter be set to 5000 milliseconds.
We can use the InetAddress class to call isReachable(int timeout) to see if the server is online.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4021) monitoring console takes too long
to recognize that a server is offline
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated GERONIMO-4021:
-----------------------------------
Fix Version/s: (was: 2.2)
Wish List
I don't see anyone implementing this for 2.2.
If we base the monitoring group on muliticast pings then we could only query servers we were pinged by recently.
> monitoring console takes too long to recognize that a server is offline
> -----------------------------------------------------------------------
>
> Key: GERONIMO-4021
> URL: https://issues.apache.org/jira/browse/GERONIMO-4021
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: monitoring
> Reporter: Viet Hung Nguyen
> Assignee: Viet Hung Nguyen
> Fix For: Wish List
>
>
> Whenever the monitoring plugin attempts to monitor a server that is offline/doesn't exist, it takes way too long to load the page. We need to reduce this timeout period.
> I suggest that we add a parameter for the admin to set as the "timeout period" somewhere in the portlet. By default, we can choose to have this timeout parameter be set to 5000 milliseconds.
> We can use the InetAddress class to call isReachable(int timeout) to see if the server is online.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4021) monitoring console takes too long
to recognize that a server is offline
Posted by "Viet Hung Nguyen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599167#action_12599167 ]
Viet Hung Nguyen commented on GERONIMO-4021:
--------------------------------------------
isReachable() uses ICMP echo requests, which aren't always supported by the destination host. This will lead to an inaccurate assessment of whether or not the server is online.
> monitoring console takes too long to recognize that a server is offline
> -----------------------------------------------------------------------
>
> Key: GERONIMO-4021
> URL: https://issues.apache.org/jira/browse/GERONIMO-4021
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: monitoring
> Reporter: Viet Hung Nguyen
> Assignee: Viet Hung Nguyen
> Fix For: 2.2
>
>
> Whenever the monitoring plugin attempts to monitor a server that is offline/doesn't exist, it takes way too long to load the page. We need to reduce this timeout period.
> I suggest that we add a parameter for the admin to set as the "timeout period" somewhere in the portlet. By default, we can choose to have this timeout parameter be set to 5000 milliseconds.
> We can use the InetAddress class to call isReachable(int timeout) to see if the server is online.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.