Issue Summary

Adding

-Dbamboo.max.concurrent.expensive.messages=2

to the JVM arguments does not increase the number of BuildTailMessageProcessingThread-expensive threads from 1 to more.

Environment

• Bamboo 6.7.2

   

Steps to Reproduce

1. Bump Bamboo heap to 4GB
2. Single plan, one job, one script task to generate a large log:

yes "HelloWorldHelloWorldHelloWorldHelloWorldHelloWorldHelloWorldHelloWorldHelloWorldHelloWorldHelloWorldHelloWorldHelloWorld" | head -n 2000000

1. Expensive regex set on the job:

(.*,\([^abc]*\):.*)

1. Run on remote agents only
2. Concurrent build limit set to 4
3. Run 4 concurrent builds of the same plan
4. Take a thread dump when the plan is finished.

Expected Results

Two BuildTailMessageProcessingThread-expensive parsing the build logs.

Actual Results

Only one BuildTailMessageProcessingThread-expensive parsing the build logs.

...

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available