Re: JDBC driver doesn't close socket event after connection.close()
From: Alin Sinpalean (alin_at_earthling.net)
Date: 02/18/05
- Next message: Hamelech Al Hakol: "Re: JDBC driver doesn't close socket event after connection.close()"
- Previous message: Joerg von Frantzius: "Long running open connections badly leak memory"
- In reply to: Hamelech Al Hakol: "Re: JDBC driver doesn't close socket event after connection.close()"
- Next in thread: Hamelech Al Hakol: "Re: JDBC driver doesn't close socket event after connection.close()"
- Reply: Hamelech Al Hakol: "Re: JDBC driver doesn't close socket event after connection.close()"
- Messages sorted by: [ date ] [ thread ]
Date: 18 Feb 2005 13:32:01 -0800
I just realized this: physical connections are created by the MS driver
(and all the other DataDirect derivatives) for each Statement in
"selectMode=direct" mode. Make sure you always close Statements or you
will end up with lots of TCP/IP connections even if you only have a
single Connection instance.
Alin,
The jTDS Project.
- Next message: Hamelech Al Hakol: "Re: JDBC driver doesn't close socket event after connection.close()"
- Previous message: Joerg von Frantzius: "Long running open connections badly leak memory"
- In reply to: Hamelech Al Hakol: "Re: JDBC driver doesn't close socket event after connection.close()"
- Next in thread: Hamelech Al Hakol: "Re: JDBC driver doesn't close socket event after connection.close()"
- Reply: Hamelech Al Hakol: "Re: JDBC driver doesn't close socket event after connection.close()"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|