Bug #36872 MYSQL TIME_WAIT issue
Submitted: 22 May 2008 5:34 Modified: 28 Sep 2010 12:37
Reporter: ravi paramasivam Email Updates:
Status: Duplicate Impact on me:
None 
Category:Tests: Server Severity:S7 (Test Cases)
Version:4.1.11-standar OS:Solaris (SunOS yamuna 5.9 Generic_117171-17 sun4u sparc SUNW,Netra-440)
Assigned to: CPU Architecture:Any

[22 May 2008 5:34] ravi paramasivam 
Description:
Mysql is the backend database configured in java application server.Whenever user makes a call app server writes the CDR information into the database.When we do a netstat -a | grep 3306 we are seeing thousands of time-wait connections.In between jdbc connection goes off/on for that database.So CDR's not getting updated.  
netstat -an | grep 3306 | wc -l reported almost 11,000 lines. With 1 listener and around 20 or so established, that means a lot of TIME_WAIT sockets. Can this be looked into?

How to repeat:
STEPS TO REPRODUCE PROBLEM
Configure the JDBC ConnectionPool in Java App Server like below JDBC ConnectionPool Configuration:- Steady Pool Size: 8 Max Pool Size: 32 Pool Resize Quantity: 2 Idle Timeout: 300 Max Wait Time: 60000 
 
Run some performance test which uses the JDBC Connection pool and writes the record in the mysql database table.
[22 May 2008 17:05] Sveta Smirnova 
Thank you for the report.

But version 4.1.11 is old. Please upgrade to current version 4.1.23 or GA 5.0.51a and infrom us if problem still exists.
[22 Jun 2008 23:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[24 Sep 2010 6:46] Gilles Rayrat 
Probably related to http://bugs.mysql.com/bug.php?id=56979
[28 Sep 2010 12:37] Sveta Smirnova 
Thank you for the feedback.

Looks very similar. Closing as duplicate of bug #56979