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

Bug 1070097

Summary: History commands sent via JMS require deploymentId to be set
Product: [Retired] JBoss BPMS Platform 6 Reporter: Ivo Bek <ibek>
Component: Business CentralAssignee: Marco Rietveld <mrietvel>
Status: CLOSED CURRENTRELEASE QA Contact: Ivo Bek <ibek>
Severity: high Docs Contact:
Priority: medium    
Version: 6.0.1CC: ibek, kverlaen, rrajasek, smcgowan
Target Milestone: ER1   
Target Release: 6.0.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 19:49:42 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
server log none

Description Ivo Bek 2014-02-26 09:01:12 UTC 
Description of problem:

For example when I use ClearHistoryLogsCommand without a deploymentId, I will get the following exception:

UnsupportedOperationException: Only commands for the task service are supported when leaving out the deployment id (ClearHistoryLogsCommand)
	at org.kie.services.client.serialization.jaxb.impl.JaxbCommandsRequest.checkThatCommandsAreTaskCommands(JaxbCommandsRequest.java:143)

Since we changed history REST operations to not require a deploymentId, I believe we should remove the requirement also from the commands.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 3 Marco Rietveld 2014-02-26 18:48:54 UTC 
Fixed. Commits: 

6.0.x: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/63fdf92c

master:
https://github.com/droolsjbpm/droolsjbpm-integration/commit/6495e3f3
Comment 4 Rajesh Rajasekaran 2014-03-14 15:40:34 UTC 
Moving to 6.0.1 based on the commit date
Comment 5 Ivo Bek 2014-03-18 12:07:51 UTC 
I return this BZ because in BPMS 6.0.1.ER2 it is not fixed yet .... see the part of DeploymentNotFoundExceptions I get:

A deployment id is required for the FindSubProcessInstancesCommand
A deployment id is required for the ClearHistoryLogsCommand
A deployment id is required for the FindProcessInstancesCommand
A deployment id is required for the FindVariableInstancesCommand
A deployment id is required for the FindNodeInstancesCommand
A deployment id is required for the FindProcessInstanceCommand
Comment 6 Marco Rietveld 2014-03-19 14:21:34 UTC 
Ivo, could you attach a stack trace showing the error? Thanks
Comment 7 Ivo Bek 2014-03-19 15:11:44 UTC 
Created attachment 876393 [details]
server log

Marco, you will find the stacktraces in the attached server log.
Comment 8 Marco Rietveld 2014-03-25 12:50:49 UTC 
Fixed. Commits: 

6.0.x: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/436600e2
https://github.com/droolsjbpm/droolsjbpm-integration/commit/2c4f88fc
https://github.com/droolsjbpm/droolsjbpm-integration/commit/1ce900e2

master: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/497805ff
https://github.com/droolsjbpm/droolsjbpm-integration/commit/be80df6c
https://github.com/droolsjbpm/droolsjbpm-integration/commit/044c4feb
Comment 9 Ivo Bek 2014-04-29 12:34:46 UTC 
Verified in BPMS 6.0.2.ER2.

The changes might have influenced the function of FindVariableInstancesByNameCommand. Here is the filed BZ 1092498.