Dear Team,
First of all, I want to apologies if there is a well known fix to my problem. Environment: OS: Windows server 2008 Tomcat application server: Apache Tomcat 7.0.63 Web server : Apache 2.2 JRE build : jdk1.6.0_23 Connection pooling: Tomcat jdbc connection pooling (Tomcat-jdbc.jar) We are having web based application hosted on Tomcat 7. We are facing close_wait issue between tomcat and database server. After certain time period close_wait count increases and reaches threshold (maxActive="500") after which tomcat was unable to create new thread and we have to restart the service. Our observation is that Oracle closes the connection and Tomcat is not able to close the same connection and hence resulting in close_wait Below is the sample netstat when CLOSE_WAIT was there. Application server is 192.168.15.109 with 219 database server listing on 1527 port. TCP 192.168.xx.xx:51588 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51621 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51622 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51623 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51632 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51647 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51648 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51658 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51659 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51691 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51699 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51705 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51706 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51722 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51724 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51725 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51744 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51805 172.16.xx.xx:1527 CLOSE_WAIT 3812 TCP 192.168.xx.xx:51807 172.16.xx.xx:1527 CLOSE_WAIT 3812 Regards, Prashant Kaujalgi Disclaimer & Privilege Notice: This e-Mail may contain proprietary, privileged and confidential information and is sent for the intended recipient(s) only. If, by an addressing or transmission error, this mail has been misdirected to you, you are requested to notify us immediately by return email message and delete this mail and its attachments. You are also hereby notified that any use, any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this e-mail message, contents or its attachment(s) other than by its intended recipient(s) is strictly prohibited. Any opinions expressed in this email are those of the individual and may not necessarily represent those of e-Nxt Financials Ltd. Before opening attachment(s), please scan for viruses.
