You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On Tuesday, February 3, 2015, we released a new cloud version of Apigee Edge.

> [!NOTE]
> **Note:** This release applies hot fixes to the previous Edge cloud release, 141029. In the management UI, the version number will continue to read 141029.01.
>
> If you have questions, contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support).
>
> For a list of all Apigee Edge release notes, see [Apigee Release Notes](https://docs.apigee.com/release/notes/apigee-release-notes).

## Bugs fixed

The following bugs are fixed in this release.

| Topic | Issue ID | Description |
|---|---|---|
| Timeouts and performance | CORERT-401 | APIs were experiencing timeouts and degraded performance. This issue has been fixed. |
| Stack traces with OAuth | CORERT-389 | Stack traces were being thrown with OAuth attempting a reverse DNS lookup. This issue has been fixed. |
| Latency with "Connection: close" header | CORERT-384 | Message processor CPU and response latencies increased whenever the target responses contained a "Connection: close" header. This issue has been fixed. |
| Http statistics | CORERT-364 | Statistics on cumulative HTTP requests and responses were incorrect. This issue has been fixed. |
| Memory utilization | CORERT-362 | High memory utilization was being caused by stop shell scripts triggered prior to process completion by message processors. This issue has been fixed. |
| ArrayIndexOutOfBoundsException with Sumo | CORERT-349 | Sumo search resulted in ArrayIndexOutOfBoundsException errors. This issue has been fixed. |
| Access Control policy X-Forward-For header | APIRT-983 | In the AccessControl policy, when more than one IP address was in the X-Forwarded-For header, the originating IP address was not being blocked. This issue has been fixed. |