Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 851299

Summary: QueryParameterException when called getTasksAssignedAsPotentialOwnerByStatusByGroup by Task client
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Alessandro Lazarotti <alazarot>
Component: jBPM 5Assignee: Kris Verlaenen <kverlaen>
Status: CLOSED UPSTREAM QA Contact: Marek Baluch <mbaluch>
Severity: high Docs Contact:
Priority: unspecified    
Version: BRMS 5.3.0.GA   
Target Milestone: ER3   
Target Release: BRMS 5.3.1 GA   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:20:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Fixed taskorm.xml none

Description Alessandro Lazarotti 2012-08-23 17:47:23 UTC
Created attachment 606668 [details]
Fixed taskorm.xml

An exception is being thrown when TaskClient.getTasksAssignedAsPotentialOwnerByStatusByGroup(userId,groupIds, statusList,language,responseHandler) is invoked:

2012-07-31 13:26:28,035 ERROR [org.jbpm.task.service.TaskServerHandler] (Thread-70) Operation failed
java.lang.RuntimeException: Operation failed
	at org.jbpm.task.service.persistence.TaskPersistenceManager.queryWithParametersInTransaction(TaskPersistenceManager.java:278)
	at org.jbpm.task.service.persistence.TaskPersistenceManager.queryWithParametersInTransaction(TaskPersistenceManager.java:285)
	at org.jbpm.task.service.TaskServiceSession.getTasksAssignedAsPotentialOwnerByStatusByGroup(TaskServiceSession.java:1034)
	at org.jbpm.task.service.TaskServerHandler.messageReceived(TaskServerHandler.java:334)
	at org.jbpm.task.service.hornetq.HornetQTaskServerHandler.messageReceived(HornetQTaskServerHandler.java:44)
	at org.jbpm.task.service.hornetq.BaseHornetQTaskServer.run(BaseHornetQTaskServer.java:85)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.IllegalArgumentException: org.hibernate.QueryParameterException: could not locate named parameter [groupIds]
	at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:234)
	at org.jbpm.task.service.persistence.TaskPersistenceManager.queryWithParameters(TaskPersistenceManager.java:314)
	at org.jbpm.task.service.persistence.TaskPersistenceManager.queryWithParametersInTransaction(TaskPersistenceManager.java:263)
	... 6 more
Caused by: org.hibernate.QueryParameterException: could not locate named parameter [groupIds]
	at org.hibernate.engine.query.ParameterMetadata.getNamedParameterDescriptor(ParameterMetadata.java:99)
	at org.hibernate.engine.query.ParameterMetadata.getNamedParameterExpectedType(ParameterMetadata.java:105)
	at org.hibernate.impl.AbstractQueryImpl.determineType(AbstractQueryImpl.java:437)
	at org.hibernate.impl.AbstractQueryImpl.setParameterList(AbstractQueryImpl.java:761)
	at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:226)
	... 8 more

Taskorm.xml looks like expecting a single groupId and not a list

Comment 1 Alessandro Lazarotti 2012-08-23 17:49:38 UTC
Fixed Taskorm.xml attached

Comment 2 Mauricio Salatino 2012-08-26 22:03:06 UTC
This is already fixed in the master I will make sure that is back ported to 5.2.x

Comment 3 Jiri Svitak 2012-10-03 08:09:31 UTC
Tested with BRMS 5.3.1 ER1 standalone and BRMS 5.3.1 ER1 ee6 deployable, but this issue has not been fixed.

Comment 4 Mauricio Salatino 2012-10-09 11:12:11 UTC
I'm fixing this issue right now, can I get more information about how you are testing this problem? 
I would like to be sure that I'm testing the fix in the same way that you are testing.

Comment 5 Jiri Svitak 2012-10-09 11:38:20 UTC
I have created a simple JUnit application which connects to the deployed human task service and the client calls the method getTasksAssignedAsPotentialOwnerByStatusByGroup(...). I have seen the described exception in the server.log.

After further investigation I have found out that the Taskorm.xml has not been fixed and I was unable to find a back port commit for this bug in 5.2.x branch.

Comment 6 Mauricio Salatino 2012-10-09 11:41:55 UTC
I've just push the fix to 5.2.x which is the branch used to build 5.3.1 ER1, as far as I know, can you test again?
Cheers

Comment 7 Mauricio Salatino 2012-10-09 11:45:22 UTC
Setting status to MODIFIED

Comment 8 Jiri Svitak 2012-10-10 11:56:54 UTC
Verified in BRMS 5.3.1 ER3.

Comment 9 lcarlon 2012-11-08 01:18:51 UTC
Hi Mauricio,

Can you review this bug to decide whether or not it should be included in the release notes, and if it should, please provide the release notes content in the doc_text field.

Thanks
Lee

Comment 13 Mauricio Salatino 2015-04-20 12:21:32 UTC
this is already solved not sure why I'm still getting notifications about this.

Comment 15 PnT Account Manager 2017-12-07 23:33:59 UTC
Employee 'msalatin' has left the company.

Comment 19 Red Hat Bugzilla 2025-02-10 03:20:36 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.