Undertow equivalent properties to jboss-web/server.xml

[thammoud]

Hello,

We are trying to undertow to match our existing JBOSS 4.x web parameters. In particular, connectionTimeout.

For example, today we have:

    <Connector port="8080" address="${jboss.bind.address}"   

         maxThreads="250" maxHttpHeaderSize="8192"

         emptySessionPath="true" protocol="HTTP/1.1"

         enableLookups="false" redirectPort="8443" acceptCount="100"

         connectionTimeout="60000" disableUploadTimeout="true" />

to establish a 60 second TTL. How do we do the same in undertow for both the timeouts and number of threads. It looks like the socket is kept alive forever. Thank you.

[ctomc]

afaik should be controlled by "task-keepalive" on worker in io subsystem.

[thammoud]

Hi Tomaz,

I do see the property. It seems to default to 60. I am assuming 60 seconds as the schema says nothing about the units. I do not see the connections reclaimed after 60 seconds like the old 4.x JBOSS used to do. My assumption is that the connection is to be closed if not subsequent HTTP(S) requests are done within 60 seconds.

[thammoud]

It looks like that is the task keep alive in the task executor. I do not believe that to be the correct property.

[renan.polo.montebelo]

Tarek,

Do you have any news on this issue? I have a server (Wildfly 8.1.0 Final w/ Undertow) that keeps connections established (netstat -aln) forever, so even with just a very few clients with time (24 hours) I get like 2K connections established. That can't be good.

Thanks in advance,

Renan

[jimarmol]

Tarek

I am having the same issue, wildfly 8.1 keeps connections alive forever. have you found any solutions? is this a bug in wildfly?

Jorge

[thammoud]

This might have been related to:

[UNDERTOW-239] Linux Pipe Leak - JBoss Issue Tracker