Bug 861987 - Error 'could not locate named parameter' when recalculating a DynaGroup query
Error 'could not locate named parameter' when recalculating a DynaGroup query
Status: NEW
Product: RHQ Project
Classification: Other
Component: Core Server (Show other bugs)
4.5
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-01 10:02 EDT by Heiko W. Rupp
Modified: 2012-10-01 10:02 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
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 2012-10-01 10:02:02 EDT
I have a DynaGroup expression like this:

groupby resource.resourceConfiguration[group]
resource.type.plugin.contains = JBossAS7
resource.type.name.contains = Managed Server

recalculation fails with

Caused by: java.lang.IllegalArgumentException: org.hibernate.QueryParameterException: could not locate named parameter [arg4]
	at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:176)
	at org.rhq.enterprise.server.resource.group.definition.framework.ExpressionEvaluator.getSingleResultList(ExpressionEvaluator.java:1027)
	at org.rhq.enterprise.server.resource.group.definition.framework.ExpressionEvaluator.access$300(ExpressionEvaluator.java:48)
	at org.rhq.enterprise.server.resource.group.definition.framework.ExpressionEvaluator$MultipleQueryIterator.next(ExpressionEvaluator.java:970)
	at org.rhq.enterprise.server.resource.group.definition.framework.ExpressionEvaluator$MultipleQueryIterator.next(ExpressionEvaluator.java:887)
	at org.rhq.enterprise.server.resource.group.definition.GroupDefinitionManagerBean.calculateGroupMembership(GroupDefinitionManagerBean.java:294)

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