Did you try to set up the fair-share configuration? Worked for me. Take a look at Work Manager: Fair Share: Configuration. Without this configuration my WL doesn't knew when was necessary apply more threads.
We don't to want prioritize allocation. We just want the Work Manager to allocate more threads than the default. The problem is that the number doesn't reach the assigned maximum value.
Vrushank, is your domain in production mode?
Yes. We are performing load testing, so we're running it in Production Mode. Also, we need each server to have equal number of threads, hence cannot use the Fair Share approach.
Can you print weblogic-ejb-jar.xml content? In developer mode, if you set a pool and max-beans-in-free-pool to lower value than your max threads in workmanager, the lower value will be the limit. I made a test with a bean set to max-beans-in-free-pool=40 (descriptor) and a custom workmanager set to max threads=100. Then sent 10.000 messages to queue and started consumption. The dashboard show me 40 bean running....
ps: check the "Ignore Stuck Threads" parameter to workmanager, I had many problems in a stress test...
ps2: See this video about workmanager from Oracle. https://www.youtube.com/watch?feature=player_embedded&v=NnRcM29zJb4
The weblogic-ejb-jar.xml content is as below:
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
The Max-Thread Constraint is also set to 400.