We're updating the issue view to help you get more done. 

It seems awfully hard to set the connector idle timeout

Description

org.ops4j.pax.web.service.jetty.internal.JettyFactory#createConnector does not accept an idleTimeout value.

So, to set the connector idle timeout (which is different from the thread idle timeout controlled by a pax-web config param), you have to explicitly define your connector in jetty.xml.

And to do that, you need to explicitly set the port in the connector to match the port from the pax web configuration, or else the pax-web code won't recognize your connector as the master.

Should there just be another pax-web param that ends up in this idleTimeout slot? Or should pax-web set some system properties that could be used in the jetty.xml to pick up the pax-web properties?

Environment

None

Status

Assignee

Unassigned

Reporter

Benson Margulies

Labels

None

Fix versions

Affects versions

4.2.4

Priority

Major