Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jsiedliski
Yak Posting Veteran
61 Posts |
 Posted - 2002-12-06 : 14:11:45
|
| My web based application has been getting the following error:----------------------------------------------[2002/12/06 06:32:34] DBComms::transmit exception:java.net.SocketException: Connection reset by peer: socket write errorcom.blastradius.spafinder.DatabaseException: DBComms::transmit exception:java.net.SocketException: Connection reset by peer: socket write error-----------------------------------------------Architecture:We have 2 IIS web servers which also run the Resin application server all running on Win 2k Servers. This is a .jsp site. Both web servers connect to 1 SQL Server (SQL Server 2k - SP2 running on Win 2k Server)I initially thought this might be a SQL Server issue. I thought it may be related to thread pooling, connections, etc. The problem usually occurs when we reach about 175 connections to the db (which I do not think is that much). It is my understanding that thread pooling does not begin until there are 255 connections.Anyway, at this point, I am thinking this is a networking issue not a database issue. Any thoughts?Sincerely,Jack |
|
|
Onamuji
Aged Yak Warrior
504 Posts |
Posted - 2002-12-06 : 14:24:51
|
| somewhere along the line your connection to the database was terminated. I've seen this happen on unstable networks/nics. network hardware failure could also be to blame. place a sniffer on your network to see were the problems source is... |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-12-06 : 14:25:45
|
| Yes, it sounds like a network problem. Connection reset by peer errors are usually due to the web server or application server doing something funky with the connections to other servers, and SQL Server is not able to maintain the connection if it gets reset. Might want to look at the application server configuration (assuming it's the one connecting to SQL Server) and look at how it's managing connections (connection limit, timeout settings, port settings/proxies/firewalls) |
|
|
|
|
|
|
Connection Reset by Peer