If you go to the auto-discovery queue page, and import a large amount of resources that take longer than 10 seconds to complete the commit to inventory, the UI will display a red "timeout" error message.
The import goes through successfully (assuming no real problems occur), but the UI just doesn't wait long enough.
As a simple solution, we have to add a timeout parameter and use it in the GWT client for the API that commits resources to inventory.
master commit 8534967
this commit bumps up the timeout to 1 minute. In addition, if that still isn't enough, we'll log a warning message that tells the user about the timeout but that the server is still processing the request.
hard to test this - I guess just import lots of resources in the discovery queue and see that you don't get a timeout (which used to be 10s - so if your request is over 10s and completes successfully, OR you get a yellow warning message, this issue is fixed)
Added for triage for RHQ4.0.1
cherry picked over to release-4.0.0 branch as commit: 9b953bd567a507e890c7ee2688c1e9c803cee88e
verified RHQ 4.0.1 by importing resources, the basic positive use-case. i am comfortable with bumping up an existing timeout value as low risk change.
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.