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.
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.
My fix for 971556 is only for availability timeouts, this fix works for other sorts of timeout issues.
Created attachment 778907 [details] patch on master (more or less)
I peer reviewed Elias' patch and it looks good to me. Commited to master: git commit to master: 82ce5f7d17b09e96bc053c19c1af5439899d8c80
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.