Bug 767215

Summary:	use of session.createReceiver() not consistent with rest of jbpm-human-task code
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Jeffrey Bride <jbride2001>
Component:	jBPM 5	Assignee:	Kris Verlaenen <kverlaen>
Status:	VERIFIED ---	QA Contact:	Lukáš Petrovický <lpetrovi>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	BRMS 5.3.0.GA
Target Milestone:	---
Target Release:	BRMS 5.3.0.GA
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Jeffrey Bride 2011-12-13 14:54:02 UTC

the use of session.createReceiver() in line 98 of org.jbpm.task.service.jms.BaseJMSTaskServer.java

is inconsistent with the use of session.createQueue() everywhere else in the jbpm-human-task functionality.

one side-affect of this is that the use of createReceiver() on a qpid JMS session does *NOT* auto-create the jbpm human-task queue if it does not already exist.  This behavior is inconsistent with the auto-creation of queues with the client-side human-task queue when using Qpid as well as both client & server side queues when using Hornetq.

thanks, jeff

Comment 1 Kris Verlaenen 2012-01-27 15:06:46 UTC

Fixed in community, should be available in next build.

Comment 3 Lukáš Petrovický 2012-05-21 07:29:23 UTC

Verified in source code. ER7.