Handling Connection Reset

I have a app server box and a DB box .
The code calls a stored proc on the DB. In between the execution of the procedure the connection between DB box and App server box is broken. What will be the state of the execution of procedure.
I mean what will be the state of the DB.
How can we handle this situation from Java JDBC ?

well ..
what i mean , wont it be in a orphan state .. like it
doenst have a connection reference to it .
It depends
In case i have a autoCommit(true) .Will the proc
commit ?
It depends.
And i dont have close on the calleable statement so
will the
session be still valid ?It depends. Although I don't really know what you mean by session.
The answer is as the same as before. It depends on the transaction state (which you have indicated) AND the database (which you have not). Of course we don't know what your proc does either (regarding transactions) and how your database handles procs (wrapping them all in a transaction perhaps) and connection failures.
So I would suggest that if you want to know what will happen with some certainty you should test.

Similar Messages

  • Socket read error: connection reset by peer

    Hi.
    Has anybody experienced the error message �Socket read error: connection reset by peer�
    Please see below for detailed information.
    Appreciate your help
    Regards
    RT
    Enviroment specification
    Server: HP/UX 11.00 64-bit, Oracle RDBMS 8.1.6.0.0 64-bit
    2 firewalls between client and db.
    Client:
    Win 2000,
    SP3,
    Oracle Client 8.1.7.0.0 ,JDBC OCI (thin JDBC driver,class12.zip)
    JDK 1.3
    JRUN3.0
    The TCP protocol is being used in the communication
    Error messages
    Web Users receive:           Socket read error: connection reset by peer
    Trace files on the sever:      Read unexpected EOF ERROR on 18.
    Explanation: The error in the server sqlnet trace file, suggests that a client connection has terminated abnormally, i.e. client machine powered off, a cable removed or a network connection aborted without warning. No user has complained of such a problem and there is no client trace with an error.
    The problem
    The users of the java web application, experiencing an exception almost once or twice a day.
    The JRUN web-server reports broken connections to the db and client are receiving "connection reset by peer".
    At the moment when the errors occurs the users just have to wait a while(2-10 min) and then they can use the web application again.(no action is taken)
    This problem can not be reproduced. The problem happens only occasionally when the network is under heavy load and new DB connection is being created.
    The application
    The java web-application uses a customized connection pooling against the database. This pool is shared among all the users of the website. whenever a user process needs to fetch data from the database, a free connection from this pool is allocated. The application is testing if the connection is valid before making a transaction (select '1' from dual). When the error occurs a ORA-3113 end-of-file on communication channel is returned to the application.
    The path between the client and db involves at least two firewalls. The firewalls are opened for sql*net traffic. The network group can tell that enquiries from the app.server is not getting feedback from the db. They have not however, identified if the enquiries are reaching the db-srever, or if they are stopped earlier in the network.
    Around 1000 users, are using other applications which uses dedicated sqlnet connections against the db and they have not experienced any problems.
    Issues considered
    Connection pooling
    It is a customized connection pooling, developed by Lindorff developers.
    I have read through the source code for the connection pooling and it does the job as it should, and in case of bad connection, it tries to create a new connection.
    The log file shows that the call to the method DriverManager.getConnection() hangs until the server goes down, which is probably because of the fact that the method DriverManager.setLoginTimeout(), does not take effect and timeout value is Zero. ( According to oracle , Oracle JDBC does not support login timeouts and calling the static DriverManager.setLoginTimeout() method will have no effect).
    Firewall
    One thing to consider is when the firewall may decide to shut down the socket due to long inactivity of a connection. This will cause problems to JDBC Connection Pool because the pool is not aware of this disconnection at the TCP/IP level; until someone checks out the connection from the pool and tries to use it. The user will get a Socket read error: connection reset by peer.
    Jrun timeout paramter is less than the firewall�s timeout so the firewall will not close a connection before Jrun does.
    Number of processes the DB can handle
    Processes parameter is 1300, , they have not experienced the Oracle error msg �max # of processes reached�.
    Port redirection through a firewall:
    Since the firewall has a sql net proxy Port redirection through a firewall is not a problem. Problems with port redirection only appear at connect time, but in this situation the connections fail long after the connection is established.
    The network group
    The network people who investigaged the problem at Lindorff report that there are a significant amount of "dropped packages" between the database server and the jdbc client (web-application) 24 hrs. The reason for this is "unknown established TCP packet" which means that the firewall does not consider these packages to be part of an already established session. The network group believes this happen because one of the hosts send a RESET or FIN signal which the firewall have noticed but are not received by the other host.
    It seems like the firewall are dropping packages bacause of "Unknown
    established TCP packet" from both the JDBC client and the TNSLISTENER on the database server. The dropped packages are SQL*Net v2 traffic so clearly Oracle products are involved

    Presumably something is working.
    Thus the problem is not with your code. At least not the database part that you have control over.
    That error occurs when the other side closes the socket. Presumably you are catching lost connection exceptions and trying to restore it.

  • Timeouts, connection reset, and EOF on socket type HTTP, etc.

    We've created our own HTTP client simulation tool to run multiple virtual users against Weblogic, but we're seeing lots of errors when we ramp up the number of virtual users. So I'm just trying to figure out if it's something about the way we're handling the sockets in the simulator, or some type of configuration on Weblogic. These are the types of messages I see in the log:
    Tue Apr 18 16:48:13 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4803,localport=7001] See property weblogic.login.readTimeoutMillis.
    Tue Apr 18 16:48:13 EDT 2000:<I> <ServletContext-Servlets> com.youcentric.servlet.LoginServlet: init
    Tue Apr 18 16:48:13 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4806,localport=7001] See property weblogic.login.readTimeoutMillis.
    Tue Apr 18 16:48:13 EDT 2000:<I> <ServletContext-Servlets> com.youcentric.servlet.LoginServlet: init
    Tue Apr 18 16:48:15 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4815,localport=7001] See property weblogic.login.readTimeoutMillis.
    Tue Apr 18 16:48:15 EDT 2000:<I> <ServletContext-Servlets> com.youcentric.servlet.LoginServlet: init
    Tue Apr 18 16:48:21 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
    Tue Apr 18 16:48:37 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4816,localport=7001] See property weblogic.login.readTimeoutMillis.
    Tue Apr 18 16:48:42 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4817,localport=7001] See property weblogic.login.readTimeoutMillis.
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:51 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:51 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Thanks in advance,
    Mike Gorman, Director of Architecture
    YOUcentric, Inc.
    Charlotte, NC
    704-643-1000 x518
    http://www.youcentric.com

    Mike,
    Try increasing the value of weblogic.login.readTimeoutMillis.
    Mike Gorman wrote:
    >
    We've created our own HTTP client simulation tool to run multiple virtual users against Weblogic, but we're seeing lots of errors when we ramp up the number of virtual users. So I'm just trying to figure out if it's something about the way we're handling the sockets in the simulator, or some type of configuration on Weblogic. These are the types of messages I see in the log:
    Tue Apr 18 16:48:13 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4803,localport=7001] See property weblogic.login.readTimeoutMillis.
    Tue Apr 18 16:48:13 EDT 2000:<I> <ServletContext-Servlets> com.youcentric.servlet.LoginServlet: init
    Tue Apr 18 16:48:13 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4806,localport=7001] See property weblogic.login.readTimeoutMillis.
    Tue Apr 18 16:48:13 EDT 2000:<I> <ServletContext-Servlets> com.youcentric.servlet.LoginServlet: init
    Tue Apr 18 16:48:15 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4815,localport=7001] See property weblogic.login.readTimeoutMillis.
    Tue Apr 18 16:48:15 EDT 2000:<I> <ServletContext-Servlets> com.youcentric.servlet.LoginServlet: init
    Tue Apr 18 16:48:21 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
    Tue Apr 18 16:48:37 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4816,localport=7001] See property weblogic.login.readTimeoutMillis.
    Tue Apr 18 16:48:42 EDT 2000:<W> <ListenThread> Connection rejected: Login timed out after 5000 msec. The socket came from [host=192.168.10.59,port=4817,localport=7001] See property weblogic.login.readTimeoutMillis.
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<E> <PosixSocketMux> connection reset on HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:47 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:51 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Tue Apr 18 16:48:51 EDT 2000:<I> <PosixSocketMux> EOF on socket type HTTP
    Thanks in advance,
    Mike Gorman, Director of Architecture
    YOUcentric, Inc.
    Charlotte, NC
    704-643-1000 x518
    http://www.youcentric.com
    Stuart Lawrence
    Software Engineer
    BEA WebXpress http://www.bea.com

  • Connection reset when uploading a report to ras server.

    Hi,
    We're running the jboss app in the linux box and use the java sdk to extract the crystal report with the ras on the remote window box. We got the below exception when extracting one of the crystal report. Any idea what's going on?
    The trace log is also attached below.
    Thanks,
    Min
    com.crystaldecisions.sdk.occa.report.lib.ReportSDKServerException: Unable to connect to the server: . - Connection reset-- Error code:-2147217387 Error code name:connectServer
    at com.crystaldecisions.sdk.occa.report.lib.ReportSDKServerException.throwReportSDKServerException(Unknown Source)
    at com.crystaldecisions.proxy.remoteagent.TCPIPCommunicationAdapter.request(Unknown Source)
    at com.crystaldecisions.proxy.remoteagent.y.a(Unknown Source)
    at com.crystaldecisions.proxy.remoteagent.r.a(Unknown Source)
    at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.if(Unknown Source)
    at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.do(Unknown Source)
    at com.crystaldecisions.sdk.occa.report.application.ReportClientDocument.a(Unknown Source)
    at com.crystaldecisions.sdk.occa.report.application.ClientDocument.open(Unknown Source)
    crystalras_xxx_ras.log
    TraceLog 2009  5  6 16:24:40.256 5892 5872 (.\dts\dts.cpp:961): CreateAgent: creating agent=8
    TraceLog 2009  5  6 16:24:40.256 5892 5216 (\servers\ras\dtsagent\cdtsagent.cpp:2463): doOneRequest saRequestId_verifyLogon in
    TraceLog 2009  5  6 16:24:40.865 5892 5216 (\servers\ras\dtsagent\cdtsagent.cpp:2465): doOneRequest saRequestId_verifyLogon out [NoError]
    TraceLog 2009  5  6 16:24:40.865 5892 5872 (.\dts\dts.cpp:1000): RemoveKey: removing agent=8
    TraceLog 2009  5  6 16:24:40.912 5892 5872 (.\dts\dts.cpp:961): CreateAgent: creating agent=9
    TraceLog 2009  5  6 16:24:40.912 5892 3152 (.\dts\cdtsagent.cpp:717): doOneRequest caReservedRequestId_CreateServerAgent in
    TraceLog 2009  5  6 16:24:40.928 5892 3152 (.\dts\cdtsagent.cpp:744): doOneRequest caReservedRequestId_CreateServerAgent out [NoError]
    TraceLog 2009  5  6 16:24:43.319 5892 3152 (.\dts\cdtsagent.cpp:749): doOneRequest caReservedRequestId_CloseServerAgent in
    TraceLog 2009  5  6 16:24:43.334 5892 3152 (.\dts\cdtsagent.cpp:757): doOneRequest caReservedRequestId_CloseServerAgent out [NoError]
    TraceLog 2009  5  6 16:24:43.334 5892 5872 (.\dts\dts.cpp:1000): RemoveKey: removing agent=9
    crystalras_xxx.log
    Timestamp     ProcessID     ThreadID     Message
    [Wed May 06 23:24:40 2009]     5892     5872     (.\dts\dts.cpp:1793): trace message:
    TraceLog 2009  5  6 16:24:40.256 5892 5872 (.\dts\dts.cpp:961): CreateAgent: creating agent=8
    [Wed May 06 23:24:40 2009]     5892     5216     trace message: XmlSerializer: before creating object
    [Wed May 06 23:24:40 2009]     5892     5216     trace message: XmlSerializer: after creating object
    [Wed May 06 23:24:40 2009]     5892     5216     (.\dts\dts.cpp:1793): trace message:
    TraceLog 2009  5  6 16:24:40.256 5892 5216 (\servers\ras\dtsagent\cdtsagent.cpp:2463): doOneRequest saRequestId_verifyLogon in
    [Wed May 06 23:24:40 2009]     5892     5216     (.\comexports.cpp:25): trace message: DllGetClassObject called.
    [Wed May 06 23:24:40 2009]     5892     5216     (y:\servers\ras\rasauditing\classfactory.h:43): trace message: Getting instance of class factory.
    [Wed May 06 23:24:40 2009]     5892     5216     (y:\servers\ras\rasauditing\classfactory.h:56): trace message: Got instance of class factory.
    [Wed May 06 23:24:40 2009]     5892     5216     (y:\servers\ras\rasauditing\classfactory.h:115): trace message: Class factory QueryInterface called.
    [Wed May 06 23:24:40 2009]     5892     5216     (y:\servers\ras\rasauditing\classfactory.h:99): trace message: Class factory addref'ed.
    [Wed May 06 23:24:40 2009]     5892     5216     (y:\servers\ras\rasauditing\classfactory.h:131): trace message: Class factory QI succeeded..
    [Wed May 06 23:24:40 2009]     5892     5216     (y:\servers\ras\rasauditing\classfactory.h:154): trace message: Attempting to create instance of COM component...
    [Wed May 06 23:24:40 2009]     5892     5216     (y:\servers\ras\rasauditing\classfactory.h:178): trace message: Successfully created COM object.
    [Wed May 06 23:24:40 2009]     5892     5216     (y:\servers\ras\rasauditing\classfactory.h:107): trace message: Class factory released.
    [Wed May 06 23:24:40 2009]     5892     5216     (.\infosessionmgr.cpp:1896): trace message: GetApslist: apsList size: 1
    [Wed May 06 23:24:40 2009]     5892     5216     (.\infosessionmgr.cpp:1897): trace message: GetApsListm_Members.GetCount()==1
    [Wed May 06 23:24:40 2009]     5892     5216     (.\infosessionmgr.cpp:1898): trace message: GetApsList m_InactiveMembers.GetSize()==0
    [Wed May 06 23:24:40 2009]     5892     5216     (.\infostore.cpp:265): trace message: CInfoStore::Query: SELECT SI_SERVER_NAME,SI_CLUSTER_NAME,SI_SERVER_IS_ALIVE,SI_SERVER_IOR,SI_SYSTEM_INFO FROM CI_SYSTEMOBJS WHERE (SI_PARENTID = 16 AND SI_SERVER_KIND = 'aps') OR SI_ID = 4
    [Wed May 06 23:24:40 2009]     5892     5216     trace message: CInfoStore::QueryEx() returned 2 objects with more to come? 0
    [Wed May 06 23:24:40 2009]     5892     5216     trace message: CInfoSessionManager::GetApsListFromNS: APS MIN.SYMYVR.LOCAL is alive.  Adding to active members
    [Wed May 06 23:24:40 2009]     5892     5216     trace message: CInfoSessionManager::ClusterInfo::UpdateRegistry: Updating min.symyvr.local; to registry
    [Wed May 06 23:24:40 2009]     5892     5216     (.\infosessionmgr.cpp:1896): trace message: GetApslist: apsList size: 1
    [Wed May 06 23:24:40 2009]     5892     5216     (.\infosessionmgr.cpp:1897): trace message: GetApsListm_Members.GetCount()==1
    [Wed May 06 23:24:40 2009]     5892     5216     (.\infosessionmgr.cpp:1898): trace message: GetApsList m_InactiveMembers.GetSize()==0
    [Wed May 06 23:24:40 2009]     5892     5216     (.\infosessionmgr.cpp:1896): trace message: GetApslist: apsList size: 1
    [Wed May 06 23:24:40 2009]     5892     5216     (.\infosessionmgr.cpp:1897): trace message: GetApsListm_Members.GetCount()==1
    [Wed May 06 23:24:40 2009]     5892     5216     (.\infosessionmgr.cpp:1898): trace message: GetApsList m_InactiveMembers.GetSize()==0
    [Wed May 06 23:24:40 2009]     5892     5216     trace message: Executing query SELECT SI_PRODUCT_VERSION FROM CI_SYSTEMOBJECTS WHERE SI_PARENTID = 26 AND SI_NAME = 'secEnterprise' to get auth properties
    [Wed May 06 23:24:40 2009]     5892     5216     (.\infostore.cpp:265): trace message: CInfoStore::Query: SELECT SI_PRODUCT_VERSION FROM CI_SYSTEMOBJECTS WHERE SI_PARENTID = 26 AND SI_NAME = 'secEnterprise'
    [Wed May 06 23:24:40 2009]     5892     5216     trace message: CInfoStore::QueryEx() returned 1 objects with more to come? 0
    [Wed May 06 23:24:40 2009]     5892     5216     trace message: ClientPing_impl::add_session_handle: session handle (23793J9ujwvkFe3QPWTsv) added
    [Wed May 06 23:24:40 2009]     5892     5216     (.\infosessionmgr.cpp:690): trace message: User: guest logged on
    [Wed May 06 23:24:40 2009]     5892     5216     trace message: ClientPing_impl::remove_session_handle: remove session handle (23793J9ujwvkFe3QPWTsv). succeded=true
    [Wed May 06 23:24:40 2009]     5892     5216     (.\proxy_impl.cpp:436): trace message: LOGOFF implicit session logoff: userId[11], m_uri[osca:iiop://MIN.SYMYVR.LOCAL/SI_SESSIONID=23793J9ujwvkFe3QPWTsv], sessionId[23793], m_sSessionHandle[23793J9ujwvkFe3QPWTsv]
    [Wed May 06 23:24:40 2009]     5892     5216     (.\dts\dts.cpp:1793): trace message:
    TraceLog 2009  5  6 16:24:40.865 5892 5216 (\servers\ras\dtsagent\cdtsagent.cpp:2465): doOneRequest saRequestId_verifyLogon out [NoError]
    [Wed May 06 23:24:40 2009]     5892     5872     (.\dts\dts.cpp:1793): trace message:
    TraceLog 2009  5  6 16:24:40.865 5892 5872 (.\dts\dts.cpp:1000): RemoveKey: removing agent=8
    [Wed May 06 23:24:40 2009]     5892     5872     (.\dts\dts.cpp:1793): trace message:
    TraceLog 2009  5  6 16:24:40.912 5892 5872 (.\dts\dts.cpp:961): CreateAgent: creating agent=9
    [Wed May 06 23:24:40 2009]     5892     3152     (.\dts\dts.cpp:1793): trace message:
    TraceLog 2009  5  6 16:24:40.912 5892 3152 (.\dts\cdtsagent.cpp:717): doOneRequest caReservedRequestId_CreateServerAgent in
    [Wed May 06 23:24:40 2009]     5892     3152     (.\dts\dts.cpp:1793): trace message:
    TraceLog 2009  5  6 16:24:40.928 5892 3152 (.\dts\cdtsagent.cpp:744): doOneRequest caReservedRequestId_CreateServerAgent out [NoError]
    [Wed May 06 23:24:43 2009]     5892     3152     (.\dts\dts.cpp:1793): trace message:
    TraceLog 2009  5  6 16:24:43.319 5892 3152 (.\dts\cdtsagent.cpp:749): doOneRequest caReservedRequestId_CloseServerAgent in
    [Wed May 06 23:24:43 2009]     5892     3152     (.\dts\dts.cpp:1793): trace message:
    TraceLog 2009  5  6 16:24:43.334 5892 3152 (.\dts\cdtsagent.cpp:757): doOneRequest caReservedRequestId_CloseServerAgent out [NoError]
    [Wed May 06 23:24:43 2009]     5892     5872     (.\dts\dts.cpp:1793): trace message:
    TraceLog 2009  5  6 16:24:43.334 5892 5872 (.\dts\dts.cpp:1000): RemoveKey: removing agent=9
    Edited by: limin9 on May 7, 2009 1:29 AM
    Edited by: limin9 on May 7, 2009 1:30 AM

    I tried to put the debug information in java code by applying clientSDKOptions.xml. And I found the report file is cut off when being passed to ras. I'm wondering if there is any file size limitation to use ras api?

  • Connection reset error while calling web service deployed on tomcat

    Hello Friends,
    I am trying to invoke a web service from web dynpro application. The web service is deployed on tomcat 5.5 server.
    I am creating an adaptive web service model using wsdl file. The model gets created without any error.
    But when application is deployed and run it is giving following exception:
    java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:168)
        at java.io.BufferedInputStream.read1(BufferedInputStream.java:254)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
        at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
        ... 102 more
    I tried to call the service from a simple java application. There the service works fine.
    Also, in the web services navigator, if I specify the wsdl url for testing it gives the same error of "Connection reset".
    I don't think this is a proxy server issue as the tomcat is within the local network.
    Can someone please help me with this?
    Thanks and regards,
    Mayuresh
    Edited by: Mayuresh Kanvinde on Mar 27, 2008 7:03 PM

    Hi Sumit,
    Thanks for the reply.
    Here is the stack trace:
    com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WSDL URL 'http://<host>:<port>/WebServicesTest/DummyWebService?wsdl' and service factory configuration 'null'
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:422)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)
         at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
         at com.tcs.vis.Vishy.<init>(Vishy.java:73)
         at com.tcs.app.AppView.wdDoInit(AppView.java:101)
         at com.tcs.app.wdp.InternalAppView.wdDoInit(InternalAppView.java:143)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
         at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:150)
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:50)
         at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:71)
         at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:91)
         at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:420)
         ... 45 more
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Problem with WSDL file parsing. See nested message.
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:182)
         at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:147)
         ... 49 more
    Caused by: com.sap.engine.lib.xml.util.NestedException: IO Exception occurred while parsing file:Connection reset -> java.net.SocketException: Connection reset
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1039)
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadWSDLDocument(WSDLDOMLoader.java:1126)
         at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:178)
         ... 50 more
    Caused by: java.net.SocketException: Connection reset
         at java.net.SocketInputStream.read(SocketInputStream.java:168)
         at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)
         at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
         at java.io.BufferedInputStream.read1(BufferedInputStream.java:220)
         at java.io.BufferedInputStream.read(BufferedInputStream.java:277)
         at com.sap.engine.services.webservices.jaxm.soap.LimitedInputStream.read(LimitedInputStream.java:61)
         at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.readData(EncodedDataReader.java:269)
         at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.fetchData(EncodedDataReader.java:332)
         at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:165)
         at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)
         at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.addInputFromInputStream(AdvancedXMLStreamReader.java:292)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:220)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
         at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
         at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
         at com.sap.engine.services.webservices.wsdl.WSDLDOMLoader.loadDOMDocument(WSDLDOMLoader.java:1023)
         ... 52 more
    Thanks and regards,
    Mayuresh
    Edited by: Mayuresh Kanvinde on Mar 28, 2008 1:10 PM

  • Connection Reset while making http web service call to remote server

    Hello guys,
    Our environment details are as follows:
    WebLogic version: 10.3.3
    Cluster: yes
    Database: Oracle
    Web service server: Remote application
    When our WebLogic server makes a http Web service call to another remote application which runs on IIS server for creating a record. The record gets created in remote application but WebLogic server log says java.net.SocketException: Connection reset and the same record doesn't get created in WebLogic application. We have confirmed that remote application is running and it is behaving as expected. Also, we installed web service client on our WebLogic machine just to isolate any network related issues, when we make a same request through this client it works fine and we get answer. At this point in time, it looks like it could be WebLogic or application which is behaving goofy. we are running out of ideas, it would be nice if someone have any thoughts on it like turning on any flags or any other troubleshooting steps. Please, let me know.
    Here is the stack trace:
    ####<Sep 18, 2011 12:31:40 AM MDT> <Info> <com.blah.blah> <server1> <WLSserver> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Defaul
    t (self-tuning)'> <user> <BEA1-69D606DA85BDB1A0A7D5> <> <1316327500388> <BEA-000000> <ERROR com.blah.blah - Error during creating a order remoteappja
    va.net.SocketException: Connection reset
    com.sun.jersey.api.client.ClientHandlerException: java.net.SocketException: Connection reset
    at com.sun.jersey.api.client.Client.handle(Client.java:569)
    at com.sun.jersey.api.client.WebResource.handle(WebResource.java:556)
    at com.sun.jersey.api.client.WebResource.access$200(WebResource.java:69)
    at com.sun.jersey.api.client.WebResource$Builder.get(WebResource.java:451)
    Caused by: java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(SocketInputStream.java:173)
    at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
    at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
    at weblogic.net.http.MessageHeader.isHTTP(MessageHeader.java:220)
    at weblogic.net.http.MessageHeader.parseHeader(MessageHeader.java:143)
    at weblogic.net.http.HttpClient.parseHTTP(HttpClient.java:462)
    at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:364)
    at weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:37)
    at weblogic.net.http.HttpURLConnection.getResponseCode(HttpURLConnection.java:952)
    at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:215)
    at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:126)
    ... 58 more
    >
    thanks a lot for your help in advance
    Regards,

    Here's what the issue was for us:
    When the web service was initializing, Weblogic? was trying to retrieve the WSDL first before initializing the service.
    Though the web service URL was proper, the WSDL itself was unresolvable. This led to this strange connection reset error.
    So, if you're experiencing this consistently, check your WSDL URL.
    We used "strace" to discover this problem by running it for a brief time while the web service initialization was attempted - and it very clearly showed that the code was attempting to laod something from a bogus address / IP

  • Connection reset error

    we wrote a proxy that should handle request from the browser and deliver it to the parent
    but when we read from the parent after we read the first chunck of data and send it to the client we get connection reset error(SocketException)
    what should we do?
    here is out code thanks
              Socket parent = null;
              PrintStream streamToParent = null;
              InputStream streamFromParent = null;
              try{
                   parent = new Socket(parentHost, parentPort);
                   //1- forword the request to the Parent ans read the response
                   streamToParent= new PrintStream(parent.getOutputStream());
                   streamToParent.write(reqStr.toString().getBytes());
                   streamToParent.flush();
                   streamToParent.println();
                   streamToParent.flush();
                   int bytesRead = -1;
                   byte[] response = new byte[4096 ];
                   //1a- extract Headers - (of response)
                   StringBuffer headers = new StringBuffer();
                   int byteRead = 0;
                   streamFromParent = parent.getInputStream();
                   while (!endOfHeaders(headers) && (byteRead = streamFromParent.read()) >= 0) {
                        headers.append((char) byteRead);
                   //1b- check headers
                   boolean toBeCached = checkResponseHeaders(headers);
                   if(toBeCached)
                        System.out.println("cachedMe: " + url.toString());
                   HttpResponseHeader resH = new HttpResponseHeader(headers.toString());
                   String etag = resH.get("ETag");
                   String lastM = resH.get("Last-Modified");
                   String expires = resH.get("Expires");
                   Date expDate = null;
                   OutputStream osBody = null;
                   byte[] bHeaders = headers.toString().getBytes("US-ASCII");
                   if(expires != null)
                        expDate = new Date(new HttpDate(expires).getAsLong());
                   //1c- write the headers to the client
                   OutputStream streamToClient = client.getOutputStream();
                   streamToClient.write(bHeaders);
                   streamToClient.flush();
                   //1d- continue with the body, read from parent and write to client
                   try{
                        if(toBeCached)
                             osBody =_wcdb.insert(url, expDate , lastM, etag, bHeaders);
                        int sumInsert = 0;
                        while ( (bytesRead = streamFromParent.read(response)) >= 0 ) {
                             streamToClient.write(response, 0 , bytesRead);
                        streamToClient.flush();
                   catch(IOException ioe)
              catch(IOException ex) {}
              finally
                   if(streamToParent != null)
                        streamToParent.close();
                   if(streamFromParent != null)
                        streamFromParent.close();
                   if(!client.isClosed())
                        client.close();
                   if(parent != null)
                        parent.close();
              }

    What 's the 'parent'?
    The exception usually means that the end you are writing to has already closed its socket. What's the full text of the exception?

  • On one website I go to for work, it says connection reset while page was loading. I was trying to change the permissions for this website but it doesn't even show up in my permission list. Help please. I need this website for work.

    I have contacted this website tech support and they say this issue is on my end. On certain pages on their web site I try go to it will say connection reset. Connection reset while page was loading. I was trying to do anything and everything I can to make sure firefox is allowing access to all pages on this website. I use this website for work I do.

    The "The connection was reset" error message can be caused by a bug fix for the BEAST (Browser Exploit Against SSL/TLS) attack that the server doesn't handle.
    *[[/questions/918127]]
    *[[/questions/918028]]
    See comment 60 in this bug report for workaround, but be aware that this makes you vulnerable to that BEAST attack.
    *[https://bugzilla.mozilla.org/show_bug.cgi?id=702111 bug 702111] - Servers intolerant to 1/n-1 record splitting. "The connection was reset"

  • Io exception: Connection reset

    Dear,
    my scenario is: SAP MII accesses an Oracle database and reads messages form this database to subsequently send to a webservice.
    For some messages, with size of 4K, the MII can complete the process successfully.
    For other messages that have size of 89K, the error occurs:
    : com.sap.xmii.Illuminator.logging.LHException: com.sap.xmii.Illuminator.logging.LHException: com.sap.xmii.Illuminator.logging.LHException: Error occurred while processing records; Io exception: Io exception: Connection reset
    How can I solve this problem?
    Best Regards,
    Sérgio Salomã

    You need to determine where the issue is occuring.  How are you calling the transaction?  Do you have proper error handling under the sql and web service actions?
    Jamie

  • Io exception: Connection reset VendorError: 17002

    When I switched from our development DB to our production DB, I now sometimes get this error when inserting a BLOB (average about 40k) using the Oracle Database 10g Release 2 (10.2.0.1.0) JDBC Drivers.
    Any help would be grealy appreciated!
    Here lies the debug:
    2006-02-27 01:32:23,996: - ERROR - (FaxTransaction.java:1209) [JavaMail-EventQueue] - SQLException: Io exception: Connection reset
    2006-02-27 01:32:23,996: - ERROR - (FaxTransaction.java:1210) [JavaMail-EventQueue] - SQLState: null
    2006-02-27 01:32:23,996: - ERROR - (FaxTransaction.java:1211) [JavaMail-EventQueue] - VendorError: 17002
    2006-02-27 01:32:23,998: - ERROR - (FaxTransaction.java:1212) [JavaMail-EventQueue] - SQLException:
    java.sql.SQLException: Io exception: Connection reset
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:255)
         at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:977)
         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168)
         at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285)
         at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3368)
         at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:101)
         at net.nighthawk.faxviewer.server.database.FaxTransaction.addFaxPage(FaxTransaction.java:1195)
         at net.nighthawk.faxviewer.server.database.FaxTransaction.addNewFaxStapleGroup(FaxTransaction.java:83)
         at net.nighthawk.faxviewer.server.mail.NewMessageHandler.handle(NewMessageHandler.java:110)
         at net.nighthawk.faxviewer.server.FaxViewerServer$NewFaxEmailHandler.messagesAdded(FaxViewerServer.java:360)
         at javax.mail.event.MessageCountEvent.dispatch(MessageCountEvent.java:137)
         at javax.mail.EventQueue.run(EventQueue.java:121)
         at java.lang.Thread.run(Thread.java:595)
    2006-02-27 01:32:24,000: - ERROR - (FaxTransaction.java:1247) [JavaMail-EventQueue] - SQLException: Closed Connection
    2006-02-27 01:32:24,000: - ERROR - (FaxTransaction.java:1248) [JavaMail-EventQueue] - SQLState: null
    2006-02-27 01:32:24,000: - ERROR - (FaxTransaction.java:1249) [JavaMail-EventQueue] - VendorError: 17008
    2006-02-27 01:32:24,001: - ERROR - (NewMessageHandler.java:118) [JavaMail-EventQueue] - SQL Error trying to get the next sequence number for the FAX PAGE STAPLE.
    java.lang.Exception: SQL Error trying to get the next sequence number for the FAX PAGE STAPLE.
         at net.nighthawk.faxviewer.server.database.FaxTransaction.addFaxStaplePage(FaxTransaction.java:1251)
         at net.nighthawk.faxviewer.server.database.FaxTransaction.addNewFaxStapleGroup(FaxTransaction.java:94)
         at net.nighthawk.faxviewer.server.mail.NewMessageHandler.handle(NewMessageHandler.java:110)
         at net.nighthawk.faxviewer.server.FaxViewerServer$NewFaxEmailHandler.messagesAdded(FaxViewerServer.java:360)
         at javax.mail.event.MessageCountEvent.dispatch(MessageCountEvent.java:137)
         at javax.mail.EventQueue.run(EventQueue.java:121)
         at java.lang.Thread.run(Thread.java:595)
    Caused by: java.sql.SQLException: Closed Connection
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
         at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:840)
         at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:759)
         at org.apache.commons.dbcp.DelegatingConnection.prepareStatement(DelegatingConnection.java:185)
         at org.apache.commons.dbcp.PoolingDriver$PoolGuardConnectionWrapper.prepareStatement(PoolingDriver.java:338)
         at net.nighthawk.faxviewer.server.database.FaxTransaction.addFaxStaplePage(FaxTransaction.java:1237)
         ... 6 more

    Here is the Java code if it helps.
    FaxPage faxPage;
    byte[] image;
    StringBuilder sqlString = new StringBuilder();
    sqlString.append("INSERT INTO faxviewer.fax_page ( ");
    sqlString.append("fax_page_id, "); // 1
    sqlString.append("fax_id, "); // 2
    sqlString.append("fax_page_number, "); // 3
    sqlString.append("fax_image ) "); //4
    sqlString.append("VALUES ( ");
    sqlString.append("?, ?, ?, ? ) ");
    stmt = conn.prepareStatement(sqlString.toString());
    stmt.setInt(1, faxPage.getFaxPageId());
    stmt.setInt(2, faxPage.getFaxId());
    stmt.setInt(3, faxPage.getFaxPageNum());
    stmt.setBytes(4, image);
    int rowcount = stmt.executeUpdate(); // Exception 17002 sometimes here

  • Socket Connection reset error

    i hava a server serving multiple clients. sometimes while reading data from the client by the thread, it is throwing an exception as follows:
    java.net.SocketException: Connection reset
    at java.net.SocketInputStream.read(SocketInputStream.java:168)
    at java.net.SocketInputStream.read(SocketInputStream.java:90)
    at Disex.Thread.clientHandlerThread.run(clientHandlerThread.java:86)
    where clientHandlerThread is my thread program to handle clients.
    i am in need of help to tackle this
    thanks
    asan

    hi...
    I think current description of your problem will not help anyone to see the issue properly. Please if you provide some detail info about your application and also if you paste the code block that is throwing exception. "Connection reset" is not saying much about your addressed issue.
    Raheel.

  • Java SocketException Connection Reset???

    Hi,
    I have written a client/server app that works fine conceptually, but eventually at some point a SocketException Connection Reset gets thrown and brings my app down. I open and close a ton of Sockets, but this error kills me. How can I preven this exception or at least catch it in a way that will stop it from bringing my app down? I would rather prevent it. Is this an error that just happens when you are opening and closing sockets? I'm using TCP sockets.

    Re: Java SocketException Connection Reset???
    I have written a client/server app that works fine
    conceptually, but eventually at some point a
    SocketException Connection Reset gets thrown and
    brings my app down.
    I open and close a ton of
    Sockets, but this error kills me. How can I preven
    this exception or at least catch it in a way that
    will stop it from bringing my app down? I would
    rather prevent it. Is this an error that just happens
    when you are opening and closing sockets? I'm using
    TCP sockets.IIRC tthis usually means the other end closed the socket
    (possibly without following the proper procedure?).
    In an application that handles many sockets,
    you should just catch the exception, close the socket in question and tidy up any resources linked to it.

  • Connection reset by peer: socket write error

    Anybody can help me?
    I run vdbench to test our NAS server, but it always failed with "
    Slave localhost-0 aborting: Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
    Error:         Windows System Error code: 64: ",  how to solve this fail ?
    conf file:
    fsd=fsd,anchor=Y:\dir,count=(11,15),depth=10,width=2,files=1,size=(10k,20,100k,20,160k,20,8m,20,10m,10,1g,5,2g,5)
    fwd=fwd1,fsd=(fsd11,fsd12,fsd13,fsd14,fsd15),rdpct=85,xfersize=(10k,22,100k,22,160k,22,8m,22,10m,12),fileio=random,fileselect=random,threads=5
    rd=rd1,fwd=fwd1,operations=read,fwdrate=max,format=yes,elapsed=10,interval=1
    logfile.html:
    14:22:49.510 Vdbench distribution: vdbench50401
    14:22:49.510
    14:22:49.526 input argument scanned: '-fcifs'
    14:22:49.526 java.vendor                   Sun Microsystems Inc.
    14:22:49.526 java.home                     C:\Program Files\Java\jre6
    14:22:49.526 java.vm.specification.version 1.0
    14:22:49.526 java.vm.version               16.3-b01
    14:22:49.526 java.vm.vendor                Sun Microsystems Inc.
    14:22:49.526 java.specification.version    1.6
    14:22:49.526 java.class.version            50.0
    14:22:49.526 user.name                     zcuser1002
    14:22:49.526 user.dir                      C:\Users\zcuser1002\Desktop\Y-vdbench-1021
    14:22:49.526 java.class.path               C:\Users\zcuser1002\Desktop\Y-vdbench-1021\;C:\Users\zcuser1002\Desktop\Y-vdbench-1021\classes;C:\Users\zcuser1002\Desktop\Y-vdbench-1021\vdbench.jar
    14:22:49.526 os.name                       Windows Server 2008 R2
    14:22:49.526 os.arch                       amd64
    14:22:49.526 os.version                    6.1
    14:22:49.526 sun.arch.data.model           64
    14:22:49.557 'fsd=fsd,count=(start,count)' added fsd11 Y:\dir11
    15:08:57.031       2704    0.0  0.00   0.9 4.42   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:08:58.030       2705  343.0 386.6   8.5 4.36   0.0    0.0  0.00  343.0 386.6  0.00 42.22  42.22  129071   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:08:59.031       2706   15.0 983.4   0.0 3.41   0.0    0.0  0.00   15.0 983.4  0.00  1.85   1.85  129160   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:09:51.406 localhost-0: anchor=Y:\dir15: Created 420 of 1024 files (41.02%)
    15:10:02.202       2707  12143 31.35   8.0 6.25   0.0    0.0  0.00  12143 31.35  0.00  1513 1513.9  130736   0.0  0.00   0.0  0.00  65.0 59795  65.0 202.8  67.0 44969   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.234       2708    0.0  0.00   8.6 8.40   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.249       2709    0.0  0.00  43.7 37.5   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00  27.0  4268   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.265       2710    0.0  0.00   0.0 0.00   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.296       2711    0.0  0.00 100.0 81.2   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.312       2712    0.0  0.00   0.0 0.00   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.312 localhost-0: 15:10:02.218 op: write  lun: Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file lba:   1484652544 0x587E0000 xfer:   131072 errno: Windows System Error code: 64: ??¡§????????????
    15:10:02.327 localhost-0: 15:10:02.234 op: write  lun: Y:\dir14\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file lba:   1971847168 0x75880000 xfer:   131072 errno: Windows System Error code: 64: ??¡§????????????
    15:10:02.343       2713    0.0  0.00 100.0 74.9   0.0    0.0  0.00    0.0  0.00  0.00  0.00   0.00       0   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00   0.0  0.00
    15:10:02.343
    15:10:02.343 **********************************************************
    15:10:02.343 Slave localhost-0 aborting: Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
    Error:         Windows System Error code: 64: ??¡§????????????
    lba:           1484652544
    xfersize:      131072
    blocks_done:   11327
    bytes_done:    1484652544
    open_for_read: false
    15:10:02.343 **********************************************************
    15:10:02.343
    15:10:18.013 Exception from slave: localhost-0
    15:10:18.013
    15:10:18.013 common.failure():
      java.net.SocketException: Connection reset by peer: socket write error
    java.net.SocketException: Connection reset by peer: socket write error
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(Unknown Source)
    at java.net.SocketOutputStream.write(Unknown Source)
    at java.io.ObjectOutputStream$BlockDataOutputStream.drain(Unknown Source)
    at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Unknown Source)
    at java.io.ObjectOutputStream.reset(Unknown Source)
    at Vdb.SlaveSocket.putMessage(SlaveSocket.java:277)
    at Vdb.CollectSlaveStats.<init>(CollectSlaveStats.java:121)
    at Vdb.Reporter.run(Reporter.java:183)
    localhost-0.stdout.html:
    stdout/stderr for slave=localhost-0
    14:22:50.072 14:22:50.072 SlaveJvm execution parameter:  '-m localhost'
    14:22:50.072 14:22:50.072 SlaveJvm execution parameter:  '-n localhost-10-141104-14.22.49.432'
    14:22:50.072 14:22:50.072 SlaveJvm execution parameter:  '-l localhost-0'
    14:22:50.072 14:22:50.072 SlaveJvm execution parameter:  '-p 5570'
    14:22:50.072 14:22:50.072 SlaveJvm positional parameter: 'SlaveJvm'
    14:22:50.118 14:22:50.118 successfully connected to master localhost
    14:22:50.118 14:22:50.118 Connection to localhost using port 5570 successful
    14:22:50.571 14:22:50.571 execute(): ls -l Y:\dir11
    14:22:50.618 14:22:50.618 execute(): ls -l Y:\dir12
    14:22:50.633 14:22:50.633 execute(): ls -l Y:\dir13
    14:22:50.664 14:22:50.664 execute(): ls -l Y:\dir14
    14:22:50.680 14:22:50.680 execute(): ls -l Y:\dir15
    14:22:50.711 14:22:50.711 Configuration interpretation took 0.45 seconds
    Link to Run Definitions:         <A HREF="#_225912260">format_for_rd1 For loops: None</A>
                                     <A HREF="#_156265924">rd1 For loops: None</A>
    14:22:50.852 14:22:50.852 Beginning of run setup
    14:22:50.852 14:22:50.852 **********************
    14:22:50.852
    14:22:50.852
    14:22:51.538 14:22:51.538 Completed the creation of the directory list for Y:\dir11: 2046 directories.
    14:22:56.811 14:22:56.811 Memory total Java heap:   77.438 MB; Free:   32.782 MB; Used:   44.655 MB;
    14:22:56.874 14:22:56.874 checkMemory()
    14:22:56.874 14:22:56.874 Memory total Java heap:   77.438 MB; Free:   52.364 MB; Used:   25.074 MB;
    14:23:03.426 14:23:03.426 Generated     1024 file names; total anchor size: 130.841g
    14:23:03.426 14:23:03.426 Writing control file for anchor=Y:\dir11 at start of run.
    14:23:03.457 14:23:03.441 Completed control file for anchor=Y:\dir11 at start of run.  dirs: 2046/2046 files: 1024/88 sizes: 130.841g/8.721g/0/0.0
    14:23:03.457 14:23:03.441 During anchor creation for anchor=Y:\dir11 there were 2046 directories and 88 files
    14:23:03.551 14:23:03.551 Completed the creation of the directory list for Y:\dir12: 2046 directories.
    14:23:08.902 14:23:08.902 Memory total Java heap:   77.438 MB; Free:   24.149 MB; Used:   53.288 MB;
    14:23:08.964 14:23:08.964 checkMemory()
    14:23:08.964 14:23:08.964 Memory total Java heap:   77.438 MB; Free:   50.640 MB; Used:   26.798 MB;
    14:23:15.579 14:23:15.579 Generated     1024 file names; total anchor size: 130.841g
    14:23:15.579 14:23:15.579 Writing control file for anchor=Y:\dir12 at start of run.
    14:23:15.594 14:23:15.594 Completed control file for anchor=Y:\dir12 at start of run.  dirs: 2046/2046 files: 1024/74 sizes: 130.841g/7.092g/0/0.0
    14:23:15.594 14:23:15.594 During anchor creation for anchor=Y:\dir12 there were 2046 directories and 74 files
    14:23:15.688 14:23:15.688 Completed the creation of the directory list for Y:\dir13: 2046 directories.
    14:23:21.210 14:23:21.210 Memory total Java heap:   74.688 MB; Free:   19.725 MB; Used:   54.963 MB;
    14:23:21.273 14:23:21.273 checkMemory()
    14:23:21.273 14:23:21.273 Memory total Java heap:   76.562 MB; Free:   48.176 MB; Used:   28.386 MB;
    14:23:28.168 14:23:28.168 Generated     1024 file names; total anchor size: 130.841g
    14:23:28.168 14:23:28.168 Writing control file for anchor=Y:\dir13 at start of run.
    14:23:28.184 14:23:28.184 Completed control file for anchor=Y:\dir13 at start of run.  dirs: 2046/2046 files: 1024/84 sizes: 130.841g/8.886g/0/0.0
    14:23:28.184 14:23:28.184 During anchor creation for anchor=Y:\dir13 there were 2046 directories and 84 files
    14:23:28.262 14:23:28.262 Completed the creation of the directory list for Y:\dir14: 2046 directories.
    14:23:33.785 14:23:33.785 Memory total Java heap:   74.250 MB; Free:   17.213 MB; Used:   57.037 MB;
    14:23:33.863 14:23:33.863 checkMemory()
    14:23:33.863 14:23:33.863 Memory total Java heap:   72.812 MB; Free:   42.829 MB; Used:   29.983 MB;
    14:23:40.976 14:23:40.976 Generated     1024 file names; total anchor size: 130.841g
    14:23:40.976 14:23:40.976 Writing control file for anchor=Y:\dir14 at start of run.
    14:23:40.976 14:23:40.976 Completed control file for anchor=Y:\dir14 at start of run.  dirs: 2046/2046 files: 1024/87 sizes: 130.841g/8.778g/0/0.0
    14:23:40.976 14:23:40.976 During anchor creation for anchor=Y:\dir14 there were 2046 directories and 87 files
    14:23:41.054 14:23:41.054 Completed the creation of the directory list for Y:\dir15: 2046 directories.
    14:23:46.296 14:23:46.296 Memory total Java heap:   74.062 MB; Free:   42.390 MB; Used:   31.672 MB;
    14:23:46.374 14:23:46.374 checkMemory()
    14:23:46.374 14:23:46.374 Memory total Java heap:  101.000 MB; Free:   68.809 MB; Used:   32.191 MB;
    14:23:52.958 14:23:52.958 Generated     1024 file names; total anchor size: 130.841g
    14:23:52.958 14:23:52.958 Writing control file for anchor=Y:\dir15 at start of run.
    14:23:52.989 14:23:52.973 Completed control file for anchor=Y:\dir15 at start of run.  dirs: 2046/2046 files: 1024/96 sizes: 130.841g/8.995g/0/0.0
    14:23:52.989 14:23:52.973 During anchor creation for anchor=Y:\dir15 there were 2046 directories and 96 files
    14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd11,operation=read:    20.0
    14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd12,operation=read:    20.0
    14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd13,operation=read:    20.0
    14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd14,operation=read:    20.0
    14:23:52.989 14:23:52.973 Skew for fwd=format,fsd=fsd15,operation=read:    20.0
    14:23:53.051 14:23:53.051 Started 8 threads for fwd=format,fsd=fsd11
    14:23:53.114 14:23:53.114 Started 8 threads for fwd=format,fsd=fsd12
    14:23:53.161 14:23:53.161 Started 8 threads for fwd=format,fsd=fsd13
    14:23:53.207 14:23:53.207 Started 8 threads for fwd=format,fsd=fsd14
    14:23:53.270 14:23:53.270 Started 8 threads for fwd=format,fsd=fsd15
    14:23:53.270 14:23:53.270 Started 40 FwgThreads
    14:23:53.270 14:23:53.270 Waiting for task synchronization
    14:23:53.270 14:23:53.270 task_wait_start_complete() end
    <a name="_225912260"></a><i><b>14:23:53.971 Starting RD=format_for_rd1</b></i>
    14:23:54.002 14:23:54.002 task_run_all(): 41 tasks
    14:23:54.051 14:23:54.051 Message to master: anchor=Y:\dir15 mkdir complete.
    14:23:54.051 14:23:54.051 Message to master: anchor=Y:\dir11 mkdir complete.
    14:23:54.051 14:23:54.051 Message to master: anchor=Y:\dir13 mkdir complete.
    14:23:54.066 14:23:54.066 Message to master: anchor=Y:\dir14 mkdir complete.
    14:23:54.066 14:23:54.066 Message to master: anchor=Y:\dir12 mkdir complete.
    14:24:24.685 14:24:24.685 Message to master: anchor=Y:\dir14: Created 130 of 1024 files (12.70%)
    14:24:56.311 14:24:56.311 Message to master: anchor=Y:\dir12: Created 130 of 1024 files (12.70%)
    14:25:40.473 14:25:40.464 Message to master: anchor=Y:\dir13: Created 140 of 1024 files (13.67%)
    14:32:52.125 14:32:52.125 Message to master: anchor=Y:\dir12: Created 140 of 1024 files (13.67%)
    14:33:30.374 14:33:30.374 Message to master: anchor=Y:\dir12: Created 160 of 1024 files (15.63%)
    14:34:33.842 14:34:33.842 Message to master: anchor=Y:\dir14: Created 170 of 1024 files (16.60%)
    14:35:49.810 14:35:49.810 Message to master: anchor=Y:\dir14: Created 180 of 1024 files (17.58%)
    14:36:34.451 14:36:34.451 Message to master: anchor=Y:\dir14: Created 190 of 1024 files (18.55%)
    14:38:13.437 14:38:13.437 Message to master: anchor=Y:\dir14: Created 200 of 1024 files (19.53%)
    14:39:01.966 14:39:01.966 Message to master: anchor=Y:\dir11: Created 210 of 1024 files (20.51%)
    14:39:57.837 14:39:57.837 Message to master: anchor=Y:\dir15: Created 220 of 1024 files (21.48%)
    14:41:51.763 14:41:51.763 Message to master: anchor=Y:\dir13: Created 220 of 1024 files (21.48%)
    14:42:31.156 14:42:31.156 Message to master: anchor=Y:\dir14: Created 240 of 1024 files (23.44%)
    14:45:32.607 14:45:32.607 Message to master: anchor=Y:\dir15: Created 260 of 1024 files (25.39%)
    14:46:44.611 14:46:44.611 Message to master: anchor=Y:\dir11: Created 270 of 1024 files (26.37%)
    14:47:53.707 14:47:53.707 Message to master: anchor=Y:\dir14: Created 280 of 1024 files (27.34%)
    14:48:25.032 14:48:25.032 Message to master: anchor=Y:\dir12: Created 280 of 1024 files (27.34%)
    14:48:56.946 14:48:56.946 Message to master: anchor=Y:\dir13: Created 290 of 1024 files (28.32%)
    14:50:40.869 14:50:40.868 Message to master: anchor=Y:\dir11: Created 300 of 1024 files (29.30%)
    14:51:22.062 14:51:22.062 Message to master: anchor=Y:\dir15: Created 330 of 1024 files (32.23%)
    14:53:55.390 14:53:55.390 Message to master: anchor=Y:\dir14: Created 350 of 1024 files (34.18%)
    14:56:20.897 14:56:20.897 Message to master: anchor=Y:\dir14: Created 360 of 1024 files (35.16%)
    14:58:08.513 14:58:08.513 Message to master: anchor=Y:\dir11: Created 360 of 1024 files (35.16%)
    14:59:34.933 14:59:34.933 Message to master: anchor=Y:\dir12: Created 360 of 1024 files (35.16%)
    15:02:15.234 15:02:15.234 Message to master: anchor=Y:\dir13: Created 370 of 1024 files (36.13%)
    15:02:48.482 15:02:48.482 Message to master: anchor=Y:\dir14: Created 380 of 1024 files (37.11%)
    15:04:27.359 15:04:27.359 Message to master: anchor=Y:\dir13: Created 380 of 1024 files (37.11%)
    15:05:57.406 15:05:57.406 Message to master: anchor=Y:\dir15: Created 390 of 1024 files (38.09%)
    15:07:18.982 15:07:18.982 Message to master: anchor=Y:\dir11: Created 390 of 1024 files (38.09%)
    15:08:15.419 15:08:15.419 Message to master: anchor=Y:\dir11: Created 410 of 1024 files (40.04%)
    15:08:50.624 15:08:50.624 Message to master: anchor=Y:\dir13: Created 410 of 1024 files (40.04%)
    15:09:51.406 15:09:51.406 Message to master: anchor=Y:\dir15: Created 420 of 1024 files (41.02%)
    15:10:02.202 15:10:02.202 file_write error2: 64
    15:10:02.202 15:10:02.202 file_write error2: 64
    15:10:02.202 15:10:02.202 handle: 0000000000000B38
    15:10:02.202 15:10:02.202 seek:   0000000075880000
    15:10:02.202 15:10:02.202 handle: 0000000000000BC0
    15:10:02.202 15:10:02.202 length: 0000000000020000
    15:10:02.202 15:10:02.202 seek:   00000000587E0000
    15:10:02.202 15:10:02.202 buffer: 0000000034430000
    15:10:02.202 15:10:02.202 length: 0000000000020000
    15:10:02.202 15:10:02.202 buffer: 000000002E3E0000
    15:10:02.234 15:10:02.234
    15:10:02.234 15:10:02.234 Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
    15:10:02.234 15:10:02.234 Error:         Windows System Error code: 64: ??¡§????????????
    15:10:02.234 15:10:02.234 lba:           1484652544
    15:10:02.234 15:10:02.234 xfersize:      131072
    15:10:02.234 15:10:02.234 blocks_done:   11327
    15:10:02.234 15:10:02.234 bytes_done:    1484652544
    15:10:02.234 15:10:02.234 open_for_read: false
    15:10:02.234 15:10:02.234
    15:10:02.234 java.lang.RuntimeException: Error writing file Y:\dir11\vdb.1_2.dir\vdb.2_2.dir\vdb.3_1.dir\vdb.4_1.dir\vdb.5_2.dir\vdb.6_2.dir\vdb.7_1.dir\vdb.8_2.dir\vdb.9_2.dir\vdb.10_1.dir\vdb_f0001.file
    15:10:02.234 Error:         Windows System Error code: 64: ??¡§????????????
    15:10:02.234 lba:           1484652544
    15:10:02.234 xfersize:      131072
    15:10:02.234 blocks_done:   11327
    15:10:02.234 bytes_done:    1484652544
    15:10:02.234 open_for_read: false
    15:10:02.234  at Vdb.common.failure(common.java:308)
    15:10:02.234  at Vdb.ActiveFile.writeError(ActiveFile.java:611)
    15:10:02.234  at Vdb.ActiveFile.writeBlock(ActiveFile.java:458)
    15:10:02.234  at Vdb.FwgThread.doSequentialWrite(FwgThread.java:327)
    15:10:02.234  at Vdb.OpCreate.doOperation(OpCreate.java:51)
    15:10:02.234  at Vdb.OpFormat.doOperation(OpFormat.java:91)
    15:10:02.234  at Vdb.FwgThread.run(FwgThread.java:157)

    'Socket write error' is merely the master finding out that the slave aborted unexpectedly.
    It it the '64' you have to worry about.
    Windows system error code 64:
    (It appears that the Vdbench translation from number to text may have some language issues and therefore can not properly print it).
    ERROR_NETNAME_DELETED
    64 (0x40)
    The specified network name is no longer available.

  • "Connection reset by peer" exceptions in JDBC

    I wonder if someone from Oracle JDBC development can answer the issues raised in
    this posting.
    component: Oracle JDBC Thin Driver
    component version: 8.1.6
    rdbms version: 8.1.5.
    Summary of problem:
    A long running application that opens JDBC connections and holds them for the lifetime of the application gets SQLExceptions with a "connection reset" message when attempting to reuse a connection that has been idle for a long period of time.
    ( The exact period is not determinable from Oracle documentation).
    We need to handle this exception and open a new connection when this happens.
    The problem is how do we determine when this exception has happened when we
    catch a SQLException. Our software is internationalized and we cant interrogate
    the message text to match for "connection reset by peer".
    The ideal way to do this is for Oracle to throw a subclass of SQLException or to
    use a error code that is unique for the "connection reset by peer" case.
    The following is a summary of the items in this message
    1. Oracle should document when the software throws away open connections.
    2. Provide documented support for handling the above SQLException in
    a language independent manner.
    3. The method isClosed() on class Connection should return true once the
    connection is rendered unusable for whatever reason ( as per the JDBC specification).
    4. The Oracle JDBC drivers should include a retry mechanism on socket errors.
    ( We dont know that whether the connection is reset by the server or if the
    client just gives up once it gets any socket error).
    business need:
    long running applications have no documented way of detecting when a connection has been discarded by the Oracle Server.
    null

    The FAQ does not answer our problem as
    it is not a server problem. The
    support person for the Server group
    asked me to look through the Alrt.log file
    for the database and there were no entries
    for that time.
    Our application has multiple threads, each having its own connection to the database, some inactive threads seem to lose their database connection. We use a driver from a third-party vendor going against SQLServer in the same network and that does not fail in this manner.
    The above seems to rule out
    1. server problems ( no, the problem is not
    happening on the first connection, but
    after the connection has been in use for
    a long time).
    2. network problems. ( the other driver is
    functioning reliably ).
    I believe that the driver may be giving up
    fairly early in the retry process.
    The only way that we know to deal with the
    problem is as follows:
    1. when a SQLException is caught, we dont
    know that the connection has been reset.
    ( we dont want to interrograte the
    message string as it will not work
    in other language environments).
    2. we just ping the connection to the server
    ( use a simple call to set the transaction
    isolation level). If this fails, we
    assume that the connection has been reset. ( Of course, we would prefer a simpler
    way like checking whether the connection
    has been closed).
    Conclusions:
    1. We feel that connections should not be
    lost in this manner.
    2. The connection loss should be detectable
    in a much more reliable manner than the
    hack we use.

  • Java.io.IOException: Connection reset by peer

    Hi,
    I'm writing a web app that has to encode jpeg to return pictures in servlet response. It seems to work fine under tomcat web server, but it crashes under iplanet when a client posts a lot of requests in a very short time : when I try to write in the ServletOutputStream, I get the following exception, and then it seems that my iplanet server doesn't handle such a case ? Any idea ?
    Thanks in advance,
    Sebastien
    java.io.IOException: Connection reset by peer
    at
    com.iplanet.server.http.servlet.NSServletSession.write(NSServletSession.java:165)
    at
    com.iplanet.server.http.servlet.NSServletOutputStream.write(NSServletOutputStream.java:252)
    at
    com.iplanet.server.http.servlet.NSServletOutputStream.write(NSServletOutputStream.java:292)
    at
    ...

    More details :
    I try to increase load by submitting lot of requests (from a single client), causing many of these requests to be aborted (I assume), so when I try to prepare the response (server side), I catch a IOException : connection reset by peer. Simultaneously, I can see in Iplanet's error logs the following snippet :
    [11/May/2004:19:04:55] failure (12789): Error accepting connection
    -5928, oserr=130 (Connect aborted) [11/May/2004:19:05:09] failure
    (12789): Error accepting connection -5928, oserr=130 (Connect aborted)
    [11/May/2004:19:05:12] failure (12789): Error accepting connection
    -5928, oserr=130 (Connect aborted)
    Any idea ?
    Sebastien

Maybe you are looking for