Here's the output: > plugins update java.lang.NullPointerException at org.rhq.plugins.postgres.PostgresUserComponent.getConnection(PostgresUserComponent.java:73) at org.rhq.plugins.postgres.PostgresUserComponent.loadResourceConfiguration(PostgresUserComponent.java:94) at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:484) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) java.lang.NullPointerException at org.rhq.plugins.postgres.PostgresUserComponent.getConnection(PostgresUserComponent.java:73) at org.rhq.plugins.postgres.PostgresUserComponent.loadResourceConfiguration(PostgresUserComponent.java:94) at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:484) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) The plugin container has been stopped. Updating plugins to their latest versions. The plugin [jopr-jboss-as-5-plugin-2.3.0-SNAPSHOT.jar] has been updated. Completed updating the plugins to their latest versions. The plugin container has been started. >
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2044
I am not able to reproduce this. I have seen something similar in the past with (I think the server component), but haven't for quite some time. Assigning to QA so they can decide if they want to followup on it or close the issue.
QA Closing - unable to repro. Can reopen if it rears its head again down the road.