On Wednesday, August 20, 2014, we released a patch for the on-premises version of Apigee
Edge.
Bugs fixed
The following bugs are fixed in this release.
Topic
Description
Netty router unresponsiveness due to buildup in the pooled connections
CORERT-219
Resolved issues which caused a connection leak when the client disconnected even before
API responses were delivered.
State machine errors in Netty router logs causing hung router
CORERT-201
When a client sent back-to-back requests on a connection without waiting for a
response, the Netty router seemed to hang and not process any requests.
A new HTTPServer.pipelining.enabled property in router.properties for the
Netty router lets you control HTTP pipelining. The following values describe the
behavior:
false (default) - If Multiple requests are received, the router returns an error
indicating the pipelining attempt and closes the connection.
true - The router handles one request at a time by buffering the requests into a
pending queue. Responses to each request are sent out in the same order as they
arrived.
In cases where a responses needs a connection closure, the connection is closed
immediately and no responses are sent for subsequent requests.
CLOSE_WAIT messages
CORERT-188
Resolved issues with CLOSED_WAIT messages that aren't properly closed.
Message processor closing connections while router tries to reuse connections from the
pool
CORERT-114
Resolved the issues causing pooled connection to be closed in certain error
conditions.
5xx errors on responsesAPIRT-342
5xx HTTP errors occurred in situations where a response was complete according to the
HTTP specification (no Content-Length or chunked encoding in target endpoint responses).
Edge now treats those responses as complete.