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

Bug 1094824

Summary: Unnecessary WARN No process instance id supplied for operation! in server log with PER_PROCESS_INSTANCE strategy
Product: [Retired] JBoss BPMS Platform 6 Reporter: Jiri Svitak <jsvitak>
Component: Business CentralAssignee: Shelly McGowan <smcgowan>
Status: CLOSED EOL QA Contact: Marek Baluch <mbaluch>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0.2CC: agiertli, mbaluch, randall_theobald
Target Milestone: ER2Keywords: Regression
Target Release: 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:43: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:
Attachments:
Description Flags
server.log none

Description Jiri Svitak 2014-05-06 14:43:02 UTC 
Created attachment 892904 [details]
server.log

Unnecessary WARN when starting a process via REST and using PER_PROCESS_INSTANCE session strategy.

15:26:04,978 WARN  [org.kie.services.remote.cdi.DeploymentInfoBean] (http-localhost.localdomain/127.0.0.1:8080-1) No process instance id supplied for operation!
15:26:06,053 WARN  [org.kie.services.remote.cdi.DeploymentInfoBean] (http-localhost.localdomain/127.0.0.1:8080-1) No process instance id supplied for operation!


To reproduce:
1.) Download BPMS 6.0.2.ER2 and patch it with files from https://bugzilla.redhat.com/show_bug.cgi?id=1092644
2.) Configure user guest with password guest. Hint:
guest=b5d048a237bfd2874b6928e1f37ee15e  (application-users.properties:)
guest=admin  (application-roles.properties:)
2.) Run the following commands to setup bpms-perf project:
curl -X POST -u "guest:guest" -H "Content-Type: application/json" -d '{"name":"bpms-assets","description":"","userName":"","password":"","requestType":"clone","gitURL":"git://git.app.eng.bos.redhat.com/bpms-assets.git"}' http://localhost:8080/business-central/rest/repositories/
curl -X POST -u "guest:guest" -H "Content-Type: application/json" -d '{"name":"qe","description":"","owner":"guest"}' http://localhost:8080/business-central/rest/organizationalunits/
curl -X POST -u "guest:guest" -H "Content-Type: application/json" http://localhost:8080/business-central/rest/organizationalunits/qe/repositories/bpms-assets/
curl -X POST -u "guest:guest" -H "Content-Type: application/json" -d '{"name":"","value":""}' http://localhost:8080/business-central/rest/repositories/bpms-assets/projects/bpms-perf/maven/deploy/
curl -X POST -u "guest:guest" -H "Content-Type: application/json" http://localhost:8080/business-central/rest/deployment/com.bpms.flood:bpms-perf:1.0.0.Final/undeploy
curl -X POST -u "guest:guest" -H "Content-Type: application/json" -d '{}' http://localhost:8080/business-central/rest/deployment/com.bpms.flood:bpms-perf:1.0.0.Final/deploy?strategy=PER_PROCESS_INSTANCE

3.) Run the process:
curl -X POST -u "guest:guest" http://localhost:8080/business-central/rest/runtime/com.bpms.flood:bpms-perf:1.0.0.Final/process/com.bpms.flood.Timer/start

Current behavior:
Unnecessary WARN is thrown in server log on each process start.

Expected behavior:
No warn is thrown on process start. I think that missing process instance id should be problem only when user wants to interact with an existing process instance. When the process is started, new process instance ID should be just created, not requested.

My env:
patched BPMS 6.0.2.ER2
EAP 6.1.1
PER_PROCESS_INSTANCE session strategy
Comment 1 Randall Theobald 2014-08-29 19:26:21 UTC 
Please fix. For high throughput environments, this adversely affects performance.
Comment 2 Marco Rietveld 2014-09-25 11:15:53 UTC 
Fixed. Given that the warning isn't helping anyone, I've just removed it. 

Commits: 

master: 
https://github.com/droolsjbpm/droolsjbpm-integration/commit/a4319ae6
Comment 3 Jiri Svitak 2014-11-21 11:53:54 UTC 
Verified in BPMS 6.1.0.ER2 using:

curl -X POST -u 'bpmsAdmin:bpmsAdmin1!' http://localhost:8080/business-central/rest/runtime/com.bpms.flood:bpms-perf:1.0.0.Final/process/com.bpms.flood.Timer/start

Checking of server logs of regular QE test plans will reveal a possible regression, so setting qe_test_coverage+.