pefernan opened a new issue, #7094:
URL: https://github.com/apache/incubator-kie/issues/7094

   ### Describe the bug
   
   When `ProcessServiceImpl.signalProcessInstance` needed to check whether a 
process instance accepts a given signal, it delegated to 
`ProcessInstances.acceptingEventType(signalName, id)`. That default method on 
`ProcessInstances` called `findById` and independently scanned 
`waitingForEventType(…) `— two separate operations that both involve 
unmarshalling the persisted process instance. This resulted in the instance 
being loaded and deserialised more than once for a single signal check, adding 
unnecessary overhead (particularly relevant for persistence-backed stores).
   
   Additionally, the `acceptingEventType` default method was defined in the 
`ProcessInstances` interface itself, mixing service-layer logic (signal 
routing) into the storage abstraction.
   
   
   
   ### Expected behavior
   
   Signaling a process instance should not cause unmarshalling unrelated 
process instances
   
   ### Actual behavior
   
   _No response_
   
   ### How to Reproduce?
   
   _No response_
   
   ### Output of `uname -a` or `ver`
   
   _No response_
   
   ### Output of `java -version`
   
   _No response_
   
   ### GraalVM version (if different from Java)
   
   _No response_
   
   ### Kogito version or git rev (or at least Quarkus version if you are using 
Kogito via Quarkus platform BOM)
   
   _No response_
   
   ### Build tool (ie. output of `mvnw --version` or `gradlew --version`)
   
   _No response_
   
   ### Additional information
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to