Bug 592980 - NPE in Get Group operation schedule
NPE in Get Group operation schedule
Status: CLOSED CURRENTRELEASE
Product: RHQ Project
Classification: Other
Component: Operations (Show other bugs)
3.0.0
All Linux
low Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Corey Welton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-17 10:32 EDT by Heiko W. Rupp
Modified: 2010-09-21 11:22 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-09-21 11:22:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Heiko W. Rupp 2010-05-17 10:32:48 EDT
2010-05-17 10:29:06,893 ERROR [org.rhq.enterprise.server.operation.OperationManagerBean] A scheduled operation has an invalid name - d
id a plugin change its operation metadata? : GroupOperationScheduleComposite: operation-job-id=[rhq-group-10011--1971580265-1274106008
943_=_rhq-group-10011], operation-name=[null], operation-next-fire-time=[Mon May 17 10:20:08 EDT 2010], group-id=[10011], group-name=[
DynaGroup - Agents], group-resource-type-name=[RHQ Agent]
java.lang.NullPointerException
        at org.rhq.enterprise.server.operation.OperationManagerBean.getGroupOperationSchedule(OperationManagerBean.java:463)
        at org.rhq.enterprise.server.operation.OperationManagerBean.getGroupOperationSchedule(OperationManagerBean.java:523)
        at org.rhq.enterprise.server.operation.OperationManagerBean.findCurrentlyScheduledGroupOperations(OperationManagerBean.java:14
73)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 
...
        at $Proxy377.findCurrentlyScheduledGroupOperations(Unknown Source)
        at org.rhq.enterprise.gui.legacy.portlet.controlactions.ViewAction.execute(ViewAction.java:95)
Comment 1 Joseph Marques 2010-09-21 11:22:50 EDT
i believe this was fixed just prior to rhq 3.0 release.  we had an issue with not properly cleaning up operations when uninventorying a resource, which caused rare errors like this.  a customer had seen this issue too, which is what drew out attention to it.  we can always re-open this bug if we ever see it again.

Note You need to log in before you can comment on or make changes to this bug.