[ https://issues.apache.org/jira/browse/TC-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hank Beatty updated TC-197: --------------------------- Fix Version/s: 2.2.0 2.1.0 > File descriptor leak caused by NIO protocol connector > ----------------------------------------------------- > > Key: TC-197 > URL: https://issues.apache.org/jira/browse/TC-197 > Project: Traffic Control > Issue Type: Bug > Components: Traffic Router > Affects Versions: 2.1.0, 2.2.0 > Reporter: Jeff Elsloo > Labels: file_descriptor_leak > Fix For: 2.1.0, 2.2.0 > > Attachments: Screen Shot 2017-03-15 at 2.12.58 PM.png > > > The new default configuration for Traffic Router and Tomcat is to use the > {{Http11NioProtocol}} adapter over the previous {{Http11Protocol}} adapter. > This is accomplished via the {{LanguidNioProtocol}} connectors specified in > Tomcat's {{server.xml}}. > We observed a file descriptor leak with connections, but have not dug into > the cause. We observed roughly 30-40k connections in {{CLOSE_WAIT}} which > caused the machine to exhaust its file descriptors based upon configured > limits. We also observed a similar growth curve on total threads, so > something is not behaving and being cleaned up appropriately. > The cause could range from a bug in the {{Http11NioProtocol}} connector due > to the ancient version of Tomcat we're using, tuning within the connector > itself (max threads, intervals, etc), tuning within the JVM (memory, GC, > etc), or at the OS level (kernel params around TCP connections, etc). -- This message was sent by Atlassian JIRA (v6.4.14#64029)