Red Hat Bugzilla – Bug 1269047
jBPM workflow take a long time to respond for a signal
Last modified: 2015-10-08 03:49:10 EDT
Description of problem:
jBPM engine takes a longer time to execute a job when multiple requests are running in background. Even a simple job takes about 45 minutes to respond.
Any subsequent signals after the first signal are properly rejected.
We need to know what is the queuing mechanism being used by jBPM for processing the jobs on the same workflow. Need some basic information on how to debug this scenario.
Version-Release number of selected component (if applicable):
Everytime in customer machine, whenever a load test is being run.
Steps to Reproduce:
1. Signal a job for a particular workflow.
2. Create a delay (or wait) in the response.
3. Signal subsequent response for the same workflow.
Response time takes about 45 min.
Response time should be immediate.
Can you please confirm which version you are using? There is only official support for BPM Suite (productized versions of jBPM), which does not include jBPM4.
We also need much more information to be able to reproduce the issue.
So please reopen the issue and specify the version of the product you are using and attach the necessary information if possible.