Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 592980 - NPE in Get Group operation schedule
Summary: NPE in Get Group operation schedule
Alias: None
Product: RHQ Project
Classification: Other
Component: Operations
Version: 3.0.0
Hardware: All
OS: Linux
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Corey Welton
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-17 14:32 UTC by Heiko W. Rupp
Modified: 2010-09-21 15:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-09-21 15:22:50 UTC

Attachments (Terms of Use)

Description Heiko W. Rupp 2010-05-17 14:32:48 UTC
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]
        at org.rhq.enterprise.server.operation.OperationManagerBean.getGroupOperationSchedule(
        at org.rhq.enterprise.server.operation.OperationManagerBean.getGroupOperationSchedule(
        at org.rhq.enterprise.server.operation.OperationManagerBean.findCurrentlyScheduledGroupOperations(
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at $Proxy377.findCurrentlyScheduledGroupOperations(Unknown Source)
        at org.rhq.enterprise.gui.legacy.portlet.controlactions.ViewAction.execute(

Comment 1 Joseph Marques 2010-09-21 15:22:50 UTC
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.