On 25 Nov 2011, at 13:45, lu zhongda wrote: > We supply java application server product to our customer. > The application server supplies jdbc connection pool functionality > to deployed web application. > The jdbc connection pool usually keeps a fixed count of physical > connections to database which are socket connections. > The support staff reflected that the connections in the connection > pool were dropped by firewall after 30mins to become idle under > customer environment . > I can't get clear information whether the firewall product is iptables. This is quite common. A lot of home routers (certainly the Netgear ones) use iptables and will drop idle connections after some configurable time. Cisco routers that track connections (for NAT or otherwise) will typically drop idle connections after some configurable interval (I think the first time I came across this in about 2001 it was 30 minutes). If you're affected by this then you need something that will keep the connection alive. In your case you need a no-op to keep the connection alive. Either that or drop your idle connections before the router does it for you. jch -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
