core-size and fallback-size not taken into account

[obouallou]

Hello,

For the standalone-server, no matter what values I put for core-size and fallback-size, I always endup with 4 runners and 8 workers. (I have 4 cores CPU)
The values are correctly set in the StandaloneWebConverterConfiguration, but I think this :

ResourceConfig resourceConfig = ResourceConfig
                .forApplication(new WebConverterApplication(configuration))
                .register(configuration);

isn't behaving as expected.

Is it a bug ?

What version of grizzly were you using ? (running 2.6 here)

[raphw]

I am using Grizzly 2.6.

I looked through the code and it seems like the pool size values are propagated correctly. What pool size did you check? Did you investigate if documents4j is sending the size values correctly?

[obouallou]

Here's a test I did with -S 10 -B 10:
https://ibb.co/dHM0rw

You can see, that the values are correction in builder, but the httpServer doesn't take them into account.

[raphw]

Yes, the server threads are controlled by Grizzly, theses sizes adjust the converters thread pool size.