max-connection attribute also works for APR endpoint and should set number of max threads that you need to increase...
please try and let me know,
I have tried the first place, it is the same connector, all the time set up with 'max-connections' to 50000.
Starting without apr, I can reach some ~40k simultaneous connections (heap size 4Gb) while the same config started with apr gives me above info when reaching some ~10k connections. Also my test tool receives timeouts on opening sockets if I try to go above that count
By looking at code, I would say that setting max-connections to 50000 for APR connector would be suecide, as this setting controls number of working threads. Default is 128.
More than that I don't know how to configure, maybe some guys from jboss web project can/will help you out.
native uses a Poller you should need a huge number of threads to handle a huge number of connections.
max-connections is the parameter to play with usually 128 X cores is a fine value for most application that why that is default.
Thank you to join this discussion. But I must admit that I don't understand your answer well. Does that mean that native has hardcoded value of the poller size(=128) which multiplies to the number of cores? And is not customizable for different number?
And other thought - If I understand correctly, native is not suitable for solving the problem of large number of open connections (eq. implementing the server push on top of async servlet 3.0), so I should stick to jio based connector?
128 X cores is the default value, but you can use max-connections to change it.
APR doesn't need on thread per connection it jsut need one thread per active request.