Bug 1248451 - PerProcessInstanceRuntimeManager should not issue a WARN message for process start commands
PerProcessInstanceRuntimeManager should not issue a WARN message for process ...
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: jBPM Core (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Maciej Swiderski
Karel Suta
Depends On:
  Show dependency treegraph
Reported: 2015-07-30 06:35 EDT by Martin Weiler
Modified: 2016-01-08 16:48 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Enhancement
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Martin Weiler 2015-07-30 06:35:48 EDT
Description of problem:
The following WARN message is emitted when a process (deployed with process instance strategy) is started with correlation key:

WARN  [org.jbpm.runtime.manager.impl.PerProcessInstanceRuntimeManager]
(http-localhost/ ProcessInstanceIdContext or
CorrelationKeyContext shall be used when interacting with
PerProcessInstance runtime manager 

As per a discussion with Marco:

"This is normal and "logical": when you _start_ a new process, there is no ProcessInstanceId- or CorrelationKeyContext yet! 

To be slightly more specific: when using a PerProcessInstanceRuntimeManager, the context is created when (after) the process instance is created. 

The problem is that in order to not have that message at that particular time, we also need to know which command is being executed: in particular, we need to know whether or not a process instance is being created or not.

The message _should_ be produced if there is already an existing process instance related to the operation ("abort process instance" or "signal process instance", for example)."

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

How reproducible:

Steps to Reproduce:
1. Create a simple process, deploy it with process instance strategy
2. Using REST command, start the process with correlation key:

<?xml version="1.0" encoding="UTF-8"?>
   <start-correlated-process processId="testWithKey">

Actual results:
Process is started, WARN message is printed

Expected results:
Process is started, no further WARN message

Additional info:

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