Created attachment 944194 [details] screen shot showing "missing description" issue Description of problem: In some cases, description field of the newly discovered resource is missing. Version-Release number of selected component (if applicable): RHQ 4.9 (or equivalent to JBoss ON 3.2.3) How reproducible: I have managed to reproduce it twice and another user saw the same behaviour quite a few times. Steps to Reproduce: 1. My box is running on Linux 2.6.35.14-106.fc14.x86_64 #1 SMP Wed Nov 23 13:07:52 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux and the result of df -T command gives: ******************************** Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/mapper/vg_bkramer-lv_root ext4 51606140 27049268 21935432 56% / tmpfs tmpfs 3993744 612 3993132 1% /dev/shm /dev/sda1 ext4 495844 49585 420659 11% /boot /dev/mapper/vg_bkramer-lv_home ext4 422717952 269655532 131589552 68% /home ******************************* The other boxes where the same behaviour has been seen are: ******************************* 1. Linux 2.6.18-274.el5 #1 SMP Fri Jul 8 17:36:59 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux 2. Linux 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux ******************************* 2. Installed JBoss ON 3.2.3 Server and Agent; 3. Navigate to JBoss ON UI and Discovery Queue; Actual results: Platform resource and RHQ Agent resource have been discovered and in the Discovery Queue but Description is missing for both or for only one of the resources. At the time when above happened, the following has been logged in the agent.log file: ******************************** 2014-09-24 14:44:43,944 WARN [InventoryManager.discovery-1] (rhq.core.pc.util.DiscoveryComponentProxyFactory)- The discovery component for resource type [ResourceType[id=0, name=File System, plugin=Platforms, category=Service]] has been blacklisted 2014-09-24 14:44:43,946 WARN [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Discovery for Resources of [ResourceType[id=0, name=File System, plugin=Platforms, category=Service]] has been running for more than 300000 milliseconds. This may be a plugin bug. org.rhq.core.pc.inventory.TimeoutException: Call to [org.rhq.plugins.platform.FileSystemDiscoveryComponent.discoverResources()] with args [[org.rhq.core.pluginapi.inventory.ResourceDiscoveryContext@712dd44f]] timed out. Invocation thread will be interrupted. at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ResourceDiscoveryComponentInvocationHandler.invokeInNewThread(DiscoveryComponentProxyFactory.java:256) at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ResourceDiscoveryComponentInvocationHandler.invoke(DiscoveryComponentProxyFactory.java:218) at com.sun.proxy.$Proxy39.discoverResources(Unknown Source) at org.rhq.core.pc.inventory.InventoryManager.invokeDiscoveryComponent(InventoryManager.java:348) at org.rhq.core.pc.inventory.InventoryManager.executeComponentDiscovery(InventoryManager.java:2682) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.discoverForResource(RuntimeDiscoveryExecutor.java:280) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.runtimeDiscover(RuntimeDiscoveryExecutor.java:142) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:105) at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:61) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: java.lang.Exception: Thread[ResourceDiscoveryComponent.invoker.daemon-1,5,main] with id [22] is hung. This exception contains its stack trace. at org.hyperic.sigar.FileSystemUsage.gather(Native Method) at org.hyperic.sigar.FileSystemUsage.fetch(FileSystemUsage.java:30) at org.hyperic.sigar.Sigar.getMountedFileSystemUsage(Sigar.java:712) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.rhq.core.system.SigarAccessHandler.invoke(SigarAccessHandler.java:128) at com.sun.proxy.$Proxy38.getMountedFileSystemUsage(Unknown Source) at org.rhq.core.system.FileSystemInfo.refresh(FileSystemInfo.java:60) at org.rhq.core.system.FileSystemInfo.<init>(FileSystemInfo.java:43) at org.rhq.core.system.NativeSystemInfo.getFileSystems(NativeSystemInfo.java:324) at org.rhq.plugins.platform.FileSystemDiscoveryComponent.discoverResources(FileSystemDiscoveryComponent.java:62) at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.rhq.core.pc.util.DiscoveryComponentProxyFactory$ComponentInvocationThread.call(DiscoveryComponentProxyFactory.java:305) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) ... 3 more 2014-09-24 14:44:43,951 INFO [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Discovery for [File System] resources took [300008] ms ******************************** On the second installation that showed the same problem the following has been logged: ******************************** 2014-09-24 13:22:07,600 DEBUG [InventoryManager.availability-1] (rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler)- Call to [org.rhq.plugins.platform.FileSystemComponent.getAvailability()] with args [] timed out after 5000 milliseconds - invocation thread will be interrupted. 2014-09-24 13:22:07,600 WARN [InventoryManager.availability-1] (rhq.core.pc.inventory.ResourceContainer$ComponentInvocation)- Invocation has been marked interrupted for method [public abstract org.rhq.core.domain.measurement.AvailabilityType org.rhq.core.pluginapi.availability.AvailabilityFacet.getAvailability()] on resource [Resource[id=10017, uuid=0f6381e0-4e4c-4b69-8000-551048c35c51, type={Platforms}File System, key=/home, name=/home, parent=bkramerlt.usersys.redhat.com]] 2014-09-24 13:22:07,600 ERROR [ResourceContainer.invoker.daemon-4] (org.rhq.core.system.FileSystemInfo)- An error occurred while refreshing the usage data for file system mounted at [/home]. java.lang.reflect.UndeclaredThrowableException at com.sun.proxy.$Proxy38.getMountedFileSystemUsage(Unknown Source) at org.rhq.core.system.FileSystemInfo.refresh(FileSystemInfo.java:60) at org.rhq.core.system.FileSystemInfo.<init>(FileSystemInfo.java:43) at org.rhq.core.system.NativeSystemInfo.getFileSystem(NativeSystemInfo.java:341) at org.rhq.plugins.platform.FileSystemComponent.getFileSystemInfo(FileSystemComponent.java:95) at org.rhq.plugins.platform.FileSystemComponent.getAvailability(FileSystemComponent.java:61) at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocation.call(ResourceContainer.java:654) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:724) Caused by: java.lang.InterruptedException at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireNanos(AbstractQueuedSynchronizer.java:934) at java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireNanos(AbstractQueuedSynchronizer.java:1245) at java.util.concurrent.locks.ReentrantLock.tryLock(ReentrantLock.java:445) at org.rhq.core.system.SigarAccessHandler.invoke(SigarAccessHandler.java:119) ... 15 more 2014-09-24 13:22:07,600 DEBUG [InventoryManager.availability-1] (rhq.core.pc.inventory.ResourceContainer$ResourceComponentInvocationHandler)- Facet lock status for [Resource[id=10017, uuid=0f6381e0-4e4c-4b69-8000-551048c35c51, type={Platforms}File System, key=/home, name=/home, parent=bkramerlt.usersys.redhat.com]], is-write-locked=[false], is-write-locked-by-current-thread=[false], read-locks=[0], waiting-for-lock-queue-size=[0] 2014-09-24 13:22:07,603 WARN [InventoryManager.availability-1] (rhq.core.pc.inventory.AvailabilityExecutor)- Availability collection timed out on Resource[id=10017, uuid=0f6381e0-4e4c-4b69-8000-551048c35c51, type={Platforms}File System, key=/home, name=/home, parent=bkramerlt.usersys.redhat.com], availability will be reported as DOWN ******************************** See also attached screen shot. Expected results: No exception is thrown and everything is properly discovered. Additional info: