d26afcb481
The issue occurred under highly concurrent request load in Go applications. Such applications are multi-threaded but use a single libunit context; any thread-safe code in the libunit context is only required for Go applications. As a result of improper request state reset, the recycled request structure was recovered in the released state, so further operations with this request resulted in 'response already sent' warnings. However, the actual response was never delivered to the router and the client.
NGINX Unit ---------- The documentation and binary packages are available online: http://unit.nginx.org The source code is provided under the terms of Apache License 2.0: http://hg.nginx.org/unit Please ask questions, report issues, and send patches to the mailing list: unit@nginx.org (http://mailman.nginx.org/mailman/listinfo/unit) or via Github: https://github.com/nginx/unit -- NGINX, Inc. http://nginx.com