I have strange behaviour in my application:
When client calls some method in stateless bean (transaction begins), there are several places where I call my thread pool , so that I expect that priority will be given more or less equally to the bean method thread and other threads which created by my thread pool.
However, I see that the thread of the running method receives priority, and only after it finishes, my threads are running.
Does anyone familiar with this behaviour? Is there something that can be changed in configuration of wildfly?
To me, this doesn't look related to thread priorities. Can you post the relevant code where you create the executor and submit the tasks? Also, how do you check/verify that these tasks are being picked up for execution after your bean method invocation completes?