Sounds like you need to understand your defer issue before making any
changes or updating versions.
On Oct 28, 2016 6:33 AM, "Nigel Vickers" wrote:
> Hallo Brad,
>
> ... thanks for the reply. The original post went under 6 weeks ago and I
> had forgotten it, sorry. We currently have a culprit an
Hallo Brad,
... thanks for the reply. The original post went under 6 weeks ago and I
had forgotten it, sorry. We currently have a culprit and a work around, and
your half right. The postgres in the backend was running out of
connections and the errors were not getting to the client. The culpri
That isn't an http2 panic. That's just the http2 code recovering your
Handler's panic and printing it, the same as the http1 server does.
Your panic is actually somewhere in:
lib.setupC5Tab(0x7f6fbe169d20, 0xc8201b0d20, 0xc820436d98, 0x7f6fbe169d20,
0xc8201b0dc0, 0x7f6fbe16a2a8, 0xc820339e60, 0x7
We are migrating an application from go 1.4.1 to 1.6.2. The application
uses a modified Gowut 0.9 as the framework and initially moved without
issue. The application server runs behind a tls sni
proxy/loadbalancer(slt). While running slt at 1.4.1 and the server at 1.6.2
no problems were encount
