Bug 959028

Summary:

Availability TimeoutException: Unclear root cause of timeouts, should display 'root cause'

Product:

[Other] RHQ Project

Reporter:

Elias Ross <genman>

Component:

Agent

Assignee:

Elias Ross <genman>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Mike Foley <mfoley>

Severity:

unspecified

Docs Contact:

Priority:

unspecified

Version:

4.5

CC:

hrupp, mazz

Target Milestone:

Target Release:

RHQ 4.10

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2014-04-23 12:32:13 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
patch on master (more or less)	none

Description Elias Ross 2013-05-03 03:04:00 UTC

Plugin container for 4.5.1

I occasionally see this for some components:

org.rhq.core.pc.inventory.TimeoutException: Call to [com....Component.getAvailability()] with args [] timed out after 5000 milliseconds - invocation thread will be interrupted.
	at org.rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler.invokeInNewThreadWithLock(ResourceContainer.java:574)
	at 

It could very well be a problem in my plugin, but rather than the stack trace of the invocation handler, can the plugin container simply display the executing thread instead? Then I can understand exactly the root cause of the thread being interrupted. (Is it trying to connect? Read data? Not doing anything?)

Alternatively, the plugin container could output a stack trace as a warning before  interrupting that thread.

Comment 1 Elias Ross 2013-06-12 18:15:19 UTC

I rolled in a fix for this for Bug 971556. If 971556 is fixed, then this is resolved as well. My fix also pretty much allows availability checking to go on for quite a while.

Comment 2 Elias Ross 2013-07-26 18:56:17 UTC

My fix for 971556 is only for availability timeouts, this fix works for other sorts of timeout issues.

Comment 3 Elias Ross 2013-07-26 23:16:25 UTC

Created attachment 778907 [details]
patch on master (more or less)

Comment 4 John Mazzitelli 2013-11-19 20:47:38 UTC

I peer reviewed Elias' patch and it looks good to me. Commited to master:

git commit to master: 82ce5f7d17b09e96bc053c19c1af5439899d8c80

Comment 5 Heiko W. Rupp 2014-04-23 12:32:13 UTC

Bulk closing of 4.10 issues.

If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.