4.14.04.10 - Apigee Edge on-premises release notes
On Wednesday, August 20, 2014, we released a patch for the on-premises version of Apigee Edge.
If you have questions, go to Apigee Customer Support.
For a list of all Apigee Edge release notes, see Apigee Release Notes.
The following bugs are fixed in this release.
|Netty router unresponsiveness due to buildup in the pooled connections
|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
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.
In cases where a responses needs a connection closure, the connection is closed immediately and no responses are sent for subsequent requests.
|Resolved issues with CLOSED_WAIT messages that aren't properly closed.|
|Message processor closing connections while router tries to reuse connections from the pool
|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.|
Help or comments?
- If something's not working: Ask the Apigee Community or see Apigee Support.
- If something's wrong with the docs: Send Docs Feedback
(Incorrect? Unclear? Broken link? Typo?)