Bug 885664 - OpenSSHD availability check may report stale data
Summary: OpenSSHD availability check may report stale data
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHQ 4.6
Assignee: Thomas Segismont
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-10 11:11 UTC by Thomas Segismont
Modified: 2013-09-03 14:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-03 14:43:04 UTC
Embargoed:

Attachments (Terms of Use)

Description Thomas Segismont 2012-12-10 11:11:24 UTC 
Description of problem:
When monitoring OpenSSHD, status update may be wrong for an arbitrary number of availability checks.

Version-Release number of selected component (if applicable):
4.6.0-SNAPSHOT

How reproducible:


Steps to Reproduce:
1.Start OpenSSHD on an monitored machine
2.When OpenSSHD availability status is "UP", close/kill OpenSSHD
  
Actual results:
The availability status is still "UP" for a time longer than the availability check interval.

Expected results:
The availability status should be "DOWN" as soon as the availability check interval has elapsed.

Additional info:
Same problem as in bug 879583 [1]

[1] https://bugzilla.redhat.com/show_bug.cgi?id=879583
Comment 1 Thomas Segismont 2012-12-10 21:09:57 UTC 
Made a fix on branch bug/885664
Comment 2 Thomas Segismont 2013-01-04 18:09:29 UTC 
Also affects MySQL
Comment 3 Thomas Segismont 2013-01-24 17:00:37 UTC 
Does not affect MySQL avail check actually
Comment 4 Thomas Segismont 2013-01-24 17:01:34 UTC 
Fixed in master 3ded44d
Comment 5 Thomas Segismont 2013-02-05 14:30:22 UTC 
Additional commit in master 187c484

The first commit introduced a refresh interval guard in ProcessInfo which is no longer needed.
Comment 6 Heiko W. Rupp 2013-09-03 14:43:04 UTC 
Bulk closing of issues in old RHQ releases that are in production for a while now.

Please open a new issue when running into an issue.
Note You need to log in before you can comment on or make changes to this bug.