[CONJ-382] Leaked Sockets when server reach maximum connections Created: 2016-10-28 Updated: 2022-09-15 Resolved: 2016-11-07 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | Other |
| Affects Version/s: | None |
| Fix Version/s: | 1.5.5, 1.1.10 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Diego Dupin | Assignee: | Diego Dupin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
reporting some issue : We are using mariadb-java-client-1.1.9 and have an issue when the maximum connections is reached on the MariaDB database. When trying to connect to a MariaDB database where the max connections was reached, the following exception is thrown: java.io.EOFException unexpected end of stream, read 0 bytes from 4. At this point the socket does not get closed and it leaks. Here is the stack trace from the Exception: The MySQLProtocol class where the exception is thrown is org.mariadb.jdbc.internal.mysql.MySQLProtocol. When we execute netstat -pan we have the following list of sockets: The socket should get properly closed in such a scenario. |
| Comments |
| Comment by Guopeng Liang [ 2022-09-15 ] |
|
For information, the bug reported in |