RE: Connection Reset Error with SQLState() = 08S01

We are having almost an identical problem, except that we are receiving an
SqlServerException: Socket closed. If you look at the trace, it seems to be
happening at exactly the same position.

19/11/2007 16:37:23.320 Thread-22200 threw
encoded.util.storage.UpdateException:
com.microsoft.sqlserver.jdbc.SQLServerException: Socket closed
at encoded.users.ServiceLogStorer.updateStorable(ServiceLogStorer.java:197)
at encoded.users.ServiceLogStorer.updateStorable(ServiceLogStorer.java:35)
at encoded.util.storage.AbstractStorer.update(AbstractStorer.java:111)
at encoded.util.storage.BackedStorable.update(BackedStorable.java:98)
at encoded.users.ServiceLog.end(ServiceLog.java:299)
at
encoded.ivr.nwo.NwoIvrService$ServiceController.resourcesFreed(NwoIvrService.java:432)
at
encoded.ivr.nwo.ResourceFactory$_FactoryListener.resourceFreed(ResourceFactory.java:489)
at
encoded.ivr.nwo.AbstractFreeable$_ResourceListenerAdapter.eventArrived(AbstractFreeable.java:267)
at
encoded.ivr.nwo.AbstractFreeable$_ResourceListenerAdapter.eventArrived(AbstractFreeable.java:245)
at
uk.co.encoded.core.util.dispatch.SimpleDispatcher$_DispatchThread.run(SimpleDispatcher.java:641)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Socket closed
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown
Source)
at com.microsoft.sqlserver.jdbc.TDSChannel.write(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSWriter.flush(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSWriter.writePacket(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSWriter.endMessage(Unknown Source)
at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(Unknown Source)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown
Source)
at
com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(Unknown
Source)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown
Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown
Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown
Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeUpdate(Unknown
Source)
at
uk.co.encoded.core.sql.StatementWrapper.executeUpdate(StatementWrapper.java:281)
at uk.co.encoded.core.sql.Odbc.executeUpdate(Odbc.java:480)
at encoded.users.ServiceLogStorer.updateServiceLog(ServiceLogStorer.java:454)
at encoded.users.ServiceLogStorer.updateStorable(ServiceLogStorer.java:194)
... 10 more


This is being run practically directly from the client to the server, with
only one switch sitting between the client and the server (no firewalls,
nothing fancy, just a normal switch). It also happens in exactly the same
place every time (whilst ending the message in order to start the response).

My gut feeling is that this isn't a network problem.



"Evan T. Basalik (MSFT)" wrote:

The vast majority of connection resets I have seen in the past are due to network hardware. It is technically possible to get it if you kill a SQL Server SPID,
but you generally know when you do that. :)

Evan
--------------------
Thread-Topic: Connection Reset Error with SQLState() = 08S01
thread-index: AcgmDkAFGmLQCwb6TMeXpIs7qVvv5w==
X-WBNR-Posting-Host: 207.46.19.168
From: =?Utf-8?B?TWFub2ogS3VtYXI=?= <ManojKumar@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <F0F1C794-A805-4370-ACA7-4F633C460104@xxxxxxxxxxxxx> <F574478C-1843-420F-95E5-D1D6F52D4382@xxxxxxxxxxxxx> <C7A101C8-
BA90-4499-8CFA-95703A3A4A8C@xxxxxxxxxxxxx> <kd32zVb6HHA.6140@xxxxxxxxxxxxxxxxxxxxxx> <4203A20E-FC68-4CD8-A81A-488ECA4286F5
@microsoft.com> <pDlOAXL9HHA.4200@xxxxxxxxxxxxxxxxxxxxxx> <C00A8E92-7A86-4480-BEDE-FC3347A65C23@xxxxxxxxxxxxx>
<rKN7lYg#HHA.360@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Connection Reset Error with SQLState() = 08S01
Date: Tue, 13 Nov 2007 08:00:02 -0800
Lines: 72
Message-ID: <5D455AB7-1900-4F31-9A16-71ECA4990944@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
Newsgroups: microsoft.public.sqlserver.jdbcdriver
Path: TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:342
NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver

We have an identical situation here at work.

So do you think the network hardware is responsible for the connection reset
issues?

TIA,
--
Manoj Kumar


"Evan T. Basalik (MSFT)" wrote:

Whenever I think about connection pooling, I usually think in terms of separating the application's connection close event from the one the server sees. If
the application "closes" a connection, the connection gets returned to the pool for use the next time the application "opens" a connection. The physical
connection to the server never gets closed.

Because the physical connection to the server is around for a long time, it is not uncommon for network hardware to either intentionally or unintentionally
sever the connection. If you use something like Netmon 3's NMCap and get a client/server trace, you can usually see a reset coming from some
intermediate piece of hardware.

Evan

--------------------
Thread-Topic: Connection Reset Error with SQLState() = 08S01
thread-index: Acf0yOITk2erIEWsT12BkkOhjdQfig==
X-WBNR-Posting-Host: 209.78.47.227
From: =?Utf-8?B?V2VzIENsYXJr?= <WesClark@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <F0F1C794-A805-4370-ACA7-4F633C460104@xxxxxxxxxxxxx> <F574478C-1843-420F-95E5-D1D6F52D4382@xxxxxxxxxxxxx>
<C7A101C8-
BA90-4499-8CFA-95703A3A4A8C@xxxxxxxxxxxxx> <kd32zVb6HHA.6140@xxxxxxxxxxxxxxxxxxxxxx> <4203A20E-FC68-4CD8-A81A-
488ECA4286F5
@microsoft.com> <pDlOAXL9HHA.4200@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Connection Reset Error with SQLState() = 08S01
Date: Tue, 11 Sep 2007 16:10:02 -0700
Lines: 15
Message-ID: <C00A8E92-7A86-4480-BEDE-FC3347A65C23@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2929
Newsgroups: microsoft.public.sqlserver.jdbcdriver
Path: TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:298
NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver

I had asked the IT guys to look at the network, and they didn't see anything
obvious. Further research led us to suspect that connections that were
sitting idle in the pool for a very long time (hours) were going dead. Is
that possible? Or does the server keep a background "keep alive"
conversation going with the client?

"Evan T. Basalik (MSFT)" wrote:

Wes,

This sounds like what would be called a general network error (GNE) in the non-JDBC world. You will likely need to take some network traces to
identify
the
cause. Most GNEs can be traced down to a piece of hardware inappropriately resetting a connection.

Evan
--------------------


Evan T. Basalik
This posting is provided “AS IS” with no warranties, and confers no rights.





Evan T. Basalik
This posting is provided “AS IS” with no warranties, and confers no rights.



.

Relevant Pages

  • Re: Outgoing POP3 email missing/lost/not received
    ... Funny thing is that I have had this ISP for 8 years and it has always been ... It looks like when you last ran CEICW, you set the ISP's mail server to: ... Internet Connection Wizard. ... After the wizard completes, the following network connection ...
    (microsoft.public.windows.server.sbs)
  • Re: Outgoing POP3 email missing/lost/not received
    ... ISP's mail server instead of the domain name on the ... SUMMARY OF SETTINGS FOR CONFIGURE E-MAIL AND INTERNET ... Internet Connection Wizard. ... After the wizard completes, the following network connection ...
    (microsoft.public.windows.server.sbs)
  • RE: Problems with Permissions
    ... And SBS server is only take ... the role of an internal server. ... they are all configured to connected to internal network. ... g. Run the Configure Email and Internet Connection Wizard on SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Networking Question - VLANs on SBS 2003 Premium SP1
    ... be sure you do not enable any DHCP server in internal network. ... You do not get any issue when you connect the SBS to the old router, ... On the Connection Type page, click Broadband, and then click Next. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connection from remote computer to network SQL Server
    ... There is no firewall on the W2K machine acting as the SQL server. ... I tried making the SQL machine a "trusted" on the router. ... connection works. ... To find the IP address of your computer inside the network, ...
    (microsoft.public.access.adp.sqlserver)
Loading