JDBC Driver: Connection reset by peer: socket write error

[chrissy]

I am using Microsoft SQL Server 2000 Driver for JDBC Service Pack 1
and on occasion receive:

"ServerXact exception: java.sql.SQLException: [Microsoft][SQLServer
2000 Driver for JDBC]Connection reset by peer: socket write error
java.lang.RuntimeException: ServerXact exception:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
JDBC]Connection reset by peer: socket write error at
com.ondemandinc.server.ServerXact$odiStatement.execute(ServerXact.java:767)
at com.ondemandinc.server.ServerXact.execute(ServerXact.java:420) at
com.ondemandinc.server.xact.DBLoginXact.execute(DBLoginXact.java:77)
at com.ondemandinc.server.web.Login.core_execute(Login.java:140) at
com.ondemandinc.server.web.Login._execute(Login.java:116) at
com.ondemandinc.server.web.Login.execute(Login.java:87) at
com.ondemandinc.server.webTask.run(webTask.java:130) at
com.ondemandinc.utils.WorkerThread.run(WorkerThread.java:88)
"

I reboot the server, it works again. The SQL Server it connects to is
SQL Server 2000 Standard Edition SP3. Any ideas what is happening?

Thanks

[Joe Weinstein]

Post by chrissy
I am using Microsoft SQL Server 2000 Driver for JDBC Service Pack 1
"ServerXact exception: java.sql.SQLException: [Microsoft][SQLServer
2000 Driver for JDBC]Connection reset by peer: socket write error
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
JDBC]Connection reset by peer: socket write error at

Yes. Either your network broke the socket between the driver
and the DBMS, or the DBMS had a failure which required it to
terminate the connection abruptly. Check the DBMS error log to
see if there are any messages about having to kill a session.
Joe Weinstein at BEA

Post by chrissy
com.ondemandinc.server.ServerXact$odiStatement.execute(ServerXact.java:767)
at com.ondemandinc.server.ServerXact.execute(ServerXact.java:420) at
com.ondemandinc.server.xact.DBLoginXact.execute(DBLoginXact.java:77)
at com.ondemandinc.server.web.Login.core_execute(Login.java:140) at
com.ondemandinc.server.web.Login._execute(Login.java:116) at
com.ondemandinc.server.web.Login.execute(Login.java:87) at
com.ondemandinc.server.webTask.run(webTask.java:130) at
com.ondemandinc.utils.WorkerThread.run(WorkerThread.java:88)
"
I reboot the server, it works again. The SQL Server it connects to is
SQL Server 2000 Standard Edition SP3. Any ideas what is happening?
Thanks

[chrissy]

Post by Joe Weinstein
Yes. Either your network broke the socket between the driver
and the DBMS, or the DBMS had a failure which required it to
terminate the connection abruptly. Check the DBMS error log to
see if there are any messages about having to kill a session.
Joe Weinstein at BEA

The DBMS has no errors in the log. In fact - when the error occurrs, I
can connect to SQL with no problem, execute queries, etc but nothing
via JDBC will work. I reboot the server that hosts both JDBC & the SQL
server and no more errors. Is this possibly a user/session limit that
we are hitting? Any way to trace exactly what happens?

[Joe Weinstein]

Post by chrissy

Post by Joe Weinstein
Yes. Either your network broke the socket between the driver
and the DBMS, or the DBMS had a failure which required it to
terminate the connection abruptly. Check the DBMS error log to
see if there are any messages about having to kill a session.
Joe Weinstein at BEA

The DBMS has no errors in the log. In fact - when the error occurrs, I
can connect to SQL with no problem, execute queries, etc but nothing
via JDBC will work. I reboot the server that hosts both JDBC & the SQL
server and no more errors. Is this possibly a user/session limit that
we are hitting? Any way to trace exactly what happens?

Very odd. It sounds like something odd with the network... When this happens,
can you *connect* via JDBC? Ie: the failure you showed was with a connection
that was already made... How many users do you have logged in via jdbc when this
happens?
Joe

[chrissy]

Joe Weinstein <***@bea.com> wrote in message news:<***@TK2MSFTNGP12.phx.gbl>...
? Any way to trace exactly what happens?

Post by Joe Weinstein
Very odd. It sounds like something odd with the network... When this happens,
can you *connect* via JDBC? Ie: the failure you showed was with a connection
that was already made... How many users do you have logged in via jdbc when this
happens?
Joe

There really shouldn't be any network interaction at all - the SQL
Server & app using JDBC are on the same machine. How can I determine
how many users are logged in using JDBC?