Bug 990490

Summary: Error msg returned when trying to get specific process variable log via REST
Product: [Retired] JBoss BPMS Platform 6 Reporter: Radovan Synek <rsynek>
Component: Business CentralAssignee: Marco Rietveld <mrietvel>
Status: CLOSED CURRENTRELEASE QA Contact: Radovan Synek <rsynek>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: rzhang, smcgowan
Target Milestone: ER2   
Target Release: 6.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-06 20:13:09 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:

Description Radovan Synek 2013-07-31 09:50:47 UTC 
After I launched a process I wanted to get a history of changes of a variable 'count':
http://localhost:8080/business-central/rest/runtime/org.jboss.qa.bpms:clustering:1.0.0.Final/history/instance/4/variable/count

However, instead of requested data I got error msg:
<response>
    <status>BAD_REQUEST</status>
    <url>/business-central/rest/runtime/org.jboss.qa.bpms:clustering:1.0.0.Final/history/instance/4/variable/count</url>
    <error>No runtime manager could be found for domain 'count'.</error>
</response>

I should mention that there are rows in the VariableInstanceLog table for this variable.

Very probably the problem is that org.kie.services.remote.rest.RuntimeResource uses the same @PathParam("id") for both deployment and variableId - take a look at the error msg: No runtime manager could be found for domain 'count'. 'count' is the name of the variable

tested with 6.0.0.CR1
Comment 1 Marco Rietveld 2013-08-09 11:09:10 UTC 
Fixed, with this commit: 

https://github.com/droolsjbpm/droolsjbpm-integration/commit/5059e60c96d2d15af9dd30661e1120bf86c69c08

(Is ER1 the right target milestone? Or ER2?)
Comment 2 Radovan Synek 2013-09-04 12:08:12 UTC 
Verified on BPMS 6.0.0.ER2