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

On Thursday, July 28, 2016, we released a new version of Apigee Edge for Private Cloud.

> [!NOTE]
> **Note:** **Questions or issues?** Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support).
>
> **Release notifications** : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications).
>
> [Release notes home page](https://docs.apigee.com/release/notes/apigee-release-notes)

## Update procedure

This release includes the update.sh utility that you use to update your
existing 4.16.05 installation to use the latest RPMs and support files. To use update.sh to update your existing 4.16.05
installation to the latest 4.16.05.01 version, see [Update Apigee Edge
4.16.05.x to latest 4.16.05 release](https://docs.apigee.com/private-cloud/v4.16.05/update-apigee-edge-41605x-latest-41605-release).

## Nodes requiring update

You only have to update the Message Processor and Edge UI components for this release,
including the Message Processor if your are using Edge Monetization. The RPMs included in
this release include:

- edge-message-processor-4.16.05-0.0.598.noarch.rpm
- edge-mint-message-processor-4.16.05-0.0.381.noarch.rpm
- edge-ui-4.16.05-0.0.3671.noarch.rpm

## Bugs fixed

The following bugs are fixed in this release.

> [!NOTE]
> **Note:** The build number in the table specifies the earliest version of the component that contains the fix. Use that build number to determine if you already have the fix installed, or if you need to perform an update. The apigee-service utility displays the build number of the currently installed component:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-service comp version
> ```
>
> where ***comp*** is the name of the component without the build number
> extension. For example:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-service apigee-setup version
> ```
>
> or get the build number of all components:
>
> ```
> /opt/apigee/apigee-service/bin/apigee-all version
> ```

| Issue ID | Description | Build number |
|---|---|---|
| APIRT-3188 | **Fix for error: java.lang.NoSuchMethodError: org.apache.commons.lang.ArrayUtils.isNotEmpty** Updated the Java language packages to support ArrayUtils.isNotEmpty(Object\[\]). | edge-message-processor-4.16.05-0.0.598 edge-mint-message-processor-4.16.05-0.0.381 |
| EDGEUI-637 | **Fix for error: Error Creating Proxy from WSDL** This error occurred when creating an API proxy from a WSDL file for a SOAP service. | edge-ui-4.16.05-0.0.3671 |

## Known issues

This release has the following known issues.

| Issue ID | Description |
|---|---|
| APIRT-2978 | **Router fails to start Nginx or Router fails to start** If the Edge Router fails to start Nginx or fails to start at all, as shown in the /opt/apigee/var/log/edge-router/logs/system.log file, then delete all files in the /opt/nginx/conf.d directory, and restart the router: ``` > rm -f /opt/nginx/conf.d/* > /opt/apigee/apigee-service/bin/apigee-service edge-router restart ``` |
| APIRT-3364 | **Message Processor does DNS lookup on IPv4 and IPv6** If you have installed and enabled NSCD (Name Service Cache Daemon) you might notice that Message Processors make two DNS lookups: one for IPv4 and one for IPv6. To disable the DNS lookup on IPv6: 1. On every Message Processor node, edit /etc/nscd.conf. 2. Set the following property: enable-cache hosts no |
| PRC-1118 | **Error when running "apigee-service apigee-postgresql pg-data-purge" command** If you run the "apigee-service apigee-postgresql pg-data-purge" command and see an error in the form: **ERROR: must be owner of relation** Edit /opt/apigee/apigee-postgresql-4.16.05-0.0.894/lib/actions/pg-data-purge and set the following property to 'apigee': POSTGRES_USER=apigee |
| DOC-1687 | **Due to a known package dependency conflict, the Katello agent used in Satellite Server 6 will not install properly on Apigee Edge hosts running the Qpid daemon.** |