Bug 1070097 - History commands sent via JMS require deploymentId to be set
Summary: History commands sent via JMS require deploymentId to be set
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ER1
: 6.0.2
Assignee: Marco Rietveld
QA Contact: Ivo Bek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-26 09:01 UTC by Ivo Bek
Modified: 2016-09-20 05:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-06 19:49:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
server log (267.09 KB, text/plain)
2014-03-19 15:11 UTC, Ivo Bek
no flags Details

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 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 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.


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