Golang TCP error wsarecv

Question

I am writing an app which listens tcp connection (see this example) . When a tcp connection disconnected I got error read tcp ip_server.:port1->ip_client:port2: wsarecv: An existing connection was forcibly closed by the remote host. I expected error EOF and timeout(for conn.SetReadDeadline()) and tried to catch error with this code:

if err != nil {     
    log.Println("getting error from listener")
    // I thought, listener can continue work another cases
    if neterr, ok := err.(net.Error); ok && neterr.Timeout() || err == io.EOF {
        log.Println("Closing connection...")
        break // connection will be closed 
    }
}

Anyone knows about this error? Do you know how to catch this error and when this error will occured ? Thanks in advance !

Not with Go but the same kind of error : stackoverflow.com/questions/2582036/… — HectorJ
– HectorJ, Commented Sep 3, 2015 at 11:04

user207421 · Accepted Answer · 2015-09-03 11:00:48Z

8

The usual cause of this error is that you sent data over a connection which had already been closed by the peer. In other words, an application protocol error.

answered Sep 3, 2015 at 11:00

user207421

312k45 gold badges324 silver badges493 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

Dave C Over a year ago

@Ulug'bekRo'zimboyev, two easy ways to find out: a) look at the Go net package source or b) use log.Printf("%T %+v", err, err) to format/print both the full type and full information contained in err when it occurs, that will tell you what code you need to replace the Printf with.

tmm1 Over a year ago

Did you find a type for this message?

levelont Over a year ago

I get

*net.OpError read tcp ip_server.:port1->ip_client:port2: wsarecv: An existing connection was forcibly closed by the remote host.

, so the type of the message should be *net.OpError.

user207421 Over a year ago

@Ulug'bekRo'zimboyev Ultimately it is ECONNRESET. What that maps to in go is unknown to me, but you might look it up.

user207421 Over a year ago

@EduardNickel Without a proper question context provided by you it is impossible to say, but have you considered the possibility that it is still an application protocol error?

Collectives™ on Stack Overflow

Golang TCP error wsarecv

1 Answer 1

5 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

5 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related