your question is way to generic to properly answer it.
What I can say is that yes we did add few more options to undertow listeners and few other areas in undertow subsystem.

But without any concrete example what you would like to have or what does not work for you I cannot help you.

and please, keep discussion about this on wildfly-dev mailing list as it is interesting topic for many people.


On Thu, May 8, 2014 at 9:28 AM, Hamed Hatami <hamedhatami2012@gmail.com> wrote:


Is it possible that in wildfly 8.1.0 hase more management on websocket connection and session at undertow ?

I wanna handle connection timeout to do somethings

Hamed Hatami

On Feb 18, 2014 1:20 PM, "Toma┼ż Cerar" <tomaz.cerar@gmail.com> wrote:

undertow has completely different semantics to what jboss web had before.

Undertow uses XNIO worker(s) which are the ones handling the thread pool and few other things.
You can configure workers in IO subsystem and tell http listener which one to use.

By default in configuration we ship we have one worker named "default" defined and all listeners use it.

But if you want to have separate workers (thread pools) per worker, all you need to do is define new worker in IO subsystem and then reference it in http-listener worker="name-of-your-worker-in-io-subsystem"

Just bit of note, we did mistake with default values for default worker in 8.0.0.Final release and will fix that in 8.0.1

In our testing we got best performance when io-threads ware set to number of logical cpus * 2 and task-max-threads set to number of cpus * 16.
This will be defaults we will probably have in 8.0.1 as they perform optimal.


On Tue, Feb 18, 2014 at 9:37 AM, Hamed Hatami <hamedhatami2012@gmail.com> wrote:

I want to use http-executor for my http-listener but it can not possible

what is the solution?

Hamed Hatami.

wildfly-dev mailing list