Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unknown message code: 3 or Unknown message code: 23

See original GitHub issue

Steps to reproduce

We have been unable to reproduce the error in a console application. It is only visible within our production environment. If we take one of our applications, and direct the connection string directly to the db rather than pgbouncer, that will cause the issue to cease. As it happens relatively frequently, we can capture some diagnostics around the issue, but cannot reproduce at will.

The issue

We’ve read all of the previous responses that we can find to this issue, and do not believe it to be a threading issue (re-using the connection). The most common instance of the issue occurs on a short lived web request during which the application uses only 1 db connection. The Unknown message codes are always either 3 or 23.

I’m curious if you have any ideas to try, or logging information to capture which may help us track down the cause.

Relevant connection string parameters:

Pooling=false

Stacktrace

{"StackTraceString":"at Npgsql.Util.PGUtil.ValidateBackendMessageCode(BackendMessageCode code)
   at Npgsql.NpgsqlConnector.<<ReadMessage>g__ReadMessageLong|194_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Npgsql.NpgsqlConnector.<ExecuteInternalCommand>d__249.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Npgsql.NpgsqlTransaction.<Commit>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Npgsql.NpgsqlTransaction.Commit()
   at NHibernate.Transaction.AdoTransaction.Commit()",
"Message":"Unknown message code: 3",
"HResult":-2147467259,
"RemoteStackTraceString":null,
"ClassName":"Npgsql.NpgsqlException",
"InnerException":null,
"Data":null,
"WatsonBuckets":null,
"ExceptionMethod":"8
ValidateBackendMessageCode
Npgsql, Version=5.0.10.0, Culture=neutral, PublicKeyToken=5d8b90d52f46fda7
Npgsql.Util.PGUtil
Void ValidateBackendMessageCode(Npgsql.BackendMessageCode)",
"RemoteStackIndex":0,
"HelpURL":null,
"Source":"Npgsql"}

Thank you beforehand for any assistance!