[embjopr-issues] [JBoss JIRA] Updated: (EMBJOPR-102) Decide whether to continuing have Availability thread running in Embedded

[Charles Crouch (JIRA)]

     [ https://jira.jboss.org/jira/browse/EMBJOPR-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Charles Crouch updated EMBJOPR-102:
-----------------------------------

    Priority: Critical  (was: Major)


Making this critical so we make sure to triage it.

> Decide whether to continuing have Availability thread running in Embedded
> -------------------------------------------------------------------------
>
>                 Key: EMBJOPR-102
>                 URL: https://jira.jboss.org/jira/browse/EMBJOPR-102
>             Project: Embedded Jopr
>          Issue Type: Task
>            Reporter: Charles Crouch
>            Priority: Critical
>             Fix For: 1.2
>
>
> Right now we have a thread running an Availability scan once a minute e.g.
> 2009-03-18 08:42:04,921 DEBUG [org.rhq.core.pc.inventory.AvailabilityExecutor] (InventoryManager.availability-1) Running Availability Scan...
> I'm wondering if it would be more prudent to have the console kickoff an availability scan at most once a minute based on usage of the console itself (i.e. use the same pattern we do for triggering service scans, i.e. on each request check if 60seconds has passed since the last run)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira