Send Docs Feedback

Note: Most user interface tasks can be performed in Edge Classic or the New Edge experience. For an overview, getting started topics, and release notes specific to the New Edge experience, see the docs.

17.02.13 - Apigee Edge for Public Cloud release notes (API runtime)

On Wednesday, March 22, 2017, we began releasing a new version of Apigee Edge for Public Cloud.

Private Cloud customers: Is this cloud release included in your Private Cloud version? See your version's release notes to see which cloud releases it contains. Also, see About release numbering to understand how you can figure it out by comparing release numbers.

Questions or issues? Get help here.

Release notifications: Go to http://status.apigee.com and click Subscribe to Updates.

Release notes home page

Removal of org.json, jmxri, and jmxtools Java libraries

The Java libraries org.json, jmxri, and jmxtools will be removed from Edge for Public Cloud in a future release after June 15, 2017. Apigee Edge no longer uses these libraries, but in case customers have leveraged this undocumented and unsupported feature, the libraries will remain on the global classpath in the short term to ensure that any API proxies containing Java Callouts that reference the libraries will continue to function out of an abundance of caution.

If you have Java Callouts that use any of these libraries, do one of the following before these libraries are removed:

  • Add the relevant JAR files as API proxy resources.
    or
  • Refactor your Java code to not use the libraries.

Note that access to these libraries has been neither documented nor supported, so this internal refactoring does not fall under the Apigee deprecation policy. (APIRT-3564, APIRT-3550)

Bugs fixed

The following bugs are fixed in this release. This list is primarily for users checking to see if their support tickets have been fixed. It's not designed to provide detailed information for all users.

Issue ID Description
DEVRT-3205 Create company fails intermittently
APIRT-3513 Proxy calls failing due to Vhost not found error
APIRT-3507 Intermittent errors on JavaScript service callouts that called the same IP with different hostnames
APIRT-3449 Policy Verify OAuth v2.0 Access Token sets wrong property name; double-prefixes apiproduct.apiproduct.*
APIRT-3392 Intermittent high response times on MPs for specific proxy
APIRT-3032 DNS lookup being done on target.url which is set to an ip address
APIRT-2718

OAuthV2 policy - Generate Access Token returns api_product_list incorrectly formatted
When using the management API to generate an OAuth v2.0 access token, the JSON response includes a list of API products in the following format:

"api_product_list" : "[Product1, Product2, Product3]"

A new api_product_list_json property in the response also returns the list of products as an array of individual product names:

"api_product_list_json" : ["Product1", "Product2", "Product3"]

 

Help or comments?