You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ go env
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\\AppData\Local\go-build
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\Users\\go
set GOPROXY=
set GORACE=
set GOROOT=C:\Go
set GOTMPDIR=
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
While using database/sql and jmoiron/sqlx modules, 99% of the time everything works fine. Occasionally, I get the following error:
failed to send SQL Batch: write tcp :58725->:1433: wsasend: An existing connection was forcibly closed by the remote host.
This happens randomly; I can't reproduce it reliably, although it seems to happen when the API (gin-gonic) hasn't handled any requests for a few minutes. It only seems to happen when API is running through IIS on my web server (tried both ASP.Net Core and HTTP Platform handlers). Could not reproduce it on my local dev machine.
Has anyone seen this at all? I have no idea how to go about diagnosing or fixing this, any help at all is much appreciated.
The text was updated successfully, but these errors were encountered:
go env
OutputWhile using database/sql and jmoiron/sqlx modules, 99% of the time everything works fine. Occasionally, I get the following error:
failed to send SQL Batch: write tcp :58725->:1433: wsasend: An existing connection was forcibly closed by the remote host.
This happens randomly; I can't reproduce it reliably, although it seems to happen when the API (gin-gonic) hasn't handled any requests for a few minutes. It only seems to happen when API is running through IIS on my web server (tried both ASP.Net Core and HTTP Platform handlers). Could not reproduce it on my local dev machine.
Has anyone seen this at all? I have no idea how to go about diagnosing or fixing this, any help at all is much appreciated.
The text was updated successfully, but these errors were encountered: