java.net.SocketException: ConnectionReset [ Edited ]

[kevincar]

OK-  Howcome / WhatFor do I get a socket exception (randomly, apparently)?

My program will randomly stop with a stack trace such as:

 faultString: java.net.SocketException: Connection reset
 faultActor:
 faultNode:
 faultDetail:
        {http://xml.apache.org/axis/}stackTrace: java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:168)
        at com.sun.net.ssl.internal.ssl.InputRecord.a(DashoA6275)
        at com.sun.net.ssl.internal.ssl.InputRecord.read(DashoA6275)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA6275)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.j(DashoA6275)
        at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(DashoA6275)
        at org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:224)
        at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:157)
        at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:114)
        at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
        at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
        at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
        at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
        at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
        at org.apache.axis.client.Call.invoke(Call.java:2553)
        at org.apache.axis.client.Call.invoke(Call.java:2248)
        at org.apache.axis.client.Call.invoke(Call.java:2171)
        at org.apache.axis.client.Call.invoke(Call.java:1691)
        at com.sforce.soap.enterprise.SoapBindingStub.update(SoapBindingStub.java:1180)
        at Insert.runInsertDemo(Insert.java:342)
        at Insert.runDemo(Insert.java:80)
        at Insert.main(Insert.java:75)

It appears to be  happening  at any time; either at 80, or even over 1000 records, apparently always on an "insert" operation.

Anyone have any thoughts/ from similar experiences?

Thanks.

KC

Message Edited by kevincar on 12-15-2003 05:10 PM

Message Edited by kevincar on 12-15-2003 05:15 PM

[kevincar]

>My program will randomly stop with a stack trace such as:
>
> faultString: java.net.SocketException: Connection reset
> faultActor:
> faultNode:
> faultDetail:
>        {http://xml.apache.org/axis/}stackTrace: java.net.SocketException: Connection reset
>        at java.net.SocketInputStream.read(SocketInputStream.java:168)
>        at com.sun.net.ssl.internal.ssl.InputRecord.a(DashoA6275)
>  ...

Hello all,
I have an update:  I appear to have solved my problem by simply
logging back in to the salesforce server.

Has anyone else ran into this problem?   Even though I'm
accessing salesforce's server thru a firewall, I don't
see how I can be the only one out there that has this
connection-reset issue.

Kevin

[adamg]

Hmm.. There were some issues with socket resets using the on Apache XML-RPC stuff (as those libs didn't leverage Java sockets correctly), but I was hopeful that the new Axis libs (I assume you are on Axis 1.1) had fixed that; personally, I've never seen the issue - can you provide more details?  Is it only on long running batch operations that the problem occurs?  Any idea how frequently its happening?

At a minimum we should be able to collectively develop some error handling code/pratices.

[kevincar]

Hi adamg,

>Hmm.. There were some issues with socket resets using the
>on Apache XML-RPC stuff (as those libs didn't leverage
>Java sockets correctly), but I was hopeful that the new
>Axis libs (I assume you are on Axis 1.1) had fixed
>that; personally, I've never seen the issue - can you
>provide more details?  Is it only on long running
>batch operations that the problem occurs?  Any idea
>how frequently its happening?

Yes,  am running Axis 1.1.  and yes, I am basically always logged on;   maybe there's a better way to do things, but I am updating the SalesForce database with current sales and personnel info on a daily basis;  I have a local database of approximately 20,000 people (each represents a SalesForce Account/Contact record) that is constantly being updated from about sixty desktops department-wide, and my java app is always logged on; basically huffing and puffing keeping up with the updates that are occurring on a real-time basis.

>At a minimum we should be able to collectively
>develop some error handling code/pratices.

The immediate solution that seems to work fine for me is to immediately call my login subroutine when a Socket ServiceException occurs.   If there is a fix/patch to the Axis libraries, I would certaily welcome it.

Kevin

Message Edited by kevincar on 01-05-2004 10:51 AM