This service will be undergoing maintenance at 00:00 UTC, 2016-08-01. It is expected to last about 1 hours

Bug 847971

Summary: Timeout for 'Scan for updates' operation is not sufficient.
Product: [Other] RHQ Project Reporter: Filip Brychta <fbrychta>
Component: Core Server, UsabilityAssignee: RHQ Project Maintainer <rhq-maint>
Status: NEW --- QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.5CC: hrupp
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description Filip Brychta 2012-08-14 04:55:33 EDT
Description of problem:
Default timeout for 'Scan for updates' is 30s but this operation usually takes longer. After 30s following warning is displayed:

Failed to scan for updated plugins. A request timeout has expired after 30000 ms. This occurred because the server is taking a long time to complete this request. Please be aware that the server may still be processing your request and it may complete shortly. You can check the server logs to see if any abnormal errors occurred.

so a user has to check server log to find out if the operation was successful.


Version-Release number of selected component (if applicable):
Version: 3.1.1.ER2
Build Number: f546515:4eb3f2c

How reproducible:
Always

Steps to Reproduce:
1. clean installation of JON prepared and running 
2. cp jon-plugin-pack-eap-3.1.1.ER2/* jon-server-3.1.1.ER2/plugins/
3. Administration->Agent plugins->Scan for Updates
  
Actual results:
Failed to scan for updated plugins. A request timeout has expired after 30000 ms. This occurred because the server is taking a long time to complete this request. Please be aware that the server may still be processing your request and it may complete shortly. You can check the server logs to see if any abnormal errors occurred.

Expected results:
A user is informed about final operation result.

Additional info:
related to bug 828296