The following sections describe the known issues with Apigee Edge. In most cases, the issues listed will be fixed in a future release.
Miscellaneous Edge known issues
The following sections describe miscellaneous known issues with Edge.
Cache expire results in incorrect cachehit value
When the cachehit flow variable is used after the
LookupCache policy, due to the way debug points are dispatched for
asynchronous behavior, the LookupPolicy populates the DebugInfo object
before the call back has executed, resulting in an error.
Workaround: Repeat the process (make second call) again right
after the first call.
Setting InvalidateCache Policy
PurgeChildEntries to true does not work correctly
Setting PurgeChildEntries in the
InvalidateCache policy should purge the KeyFragment element values only but
clears the entire cache.
For example, the following features from the OpenAPI Specification 3.0 are not yet supported:
allOf properties for combining and extending schemas
If an unsupported feature is referenced in your OpenAPI Specification, in some cases the tools will ignore the feature but still
render the API reference documentation. In other cases, an unsupported feature will cause errors that prevent the successful rendering
of the API reference documentation. In either case, you will need to modify your OpenAPI Specification to avoid use of the unsupported
feature until it is supported in a future release.
Note: Because the spec editor is less restrictive than SmartDocs when rendering API reference documentation,
you may experience different results between the tools.
When using Try this API in the portal, the Accept header is set to application/json regardless of the value set for consumes in the OpenAPI Specification.
SAML identity provider
Single logout (SLO) with the SAML identity provider is not supported for custom domains. To enable a custom domain with a SAML identity provider, leave
the Sign-out URL field blank
when you configure SAML settings.
Simultaneous portal updates (such as page, theme, CSS, or script edits) by multiple users is not supported at this time.
If you delete an API reference documentation page from the portal, there is no way to recreate it; you'll need to delete and re-add
the API product, and regenerate the API reference documentation.
Search will be integrated into the integrated portal in a future release.
Known issues with Edge for Private Cloud
The following sections describe the known issues with Edge for Private Cloud.
Apigee HTTP/2 Vulnerability
A Denial-of-Service (DoS) vulnerability was recently discovered in multiple
implementations of the HTTP/2 protocol (CVE-2023-44487), including in Apigee Edge for
Private Cloud. The vulnerability could lead to a DoS of Apigee API management functionality.
For more details, see Apigee Security Bulletin GCP-2023-032.
The Edge for Private Cloud router and management server components are exposed to the
internet and can potentially be vulnerable. Although HTTP/2 is enabled on the management
port of other Edge-specific components of Edge for Private Cloud, none of those components are
exposed to the internet. On non-Edge components, like Cassandra, Zookeeper and others,
HTTP/2 is not enabled. We recommend that you take the
following steps to address the Edge for Private Cloud vulnerability:
apigee-mirror does not work on Red Hat Enterprise Linux (RHEL) 8.0.
As a workaround, install apigee-mirror on a server running a lower version
of RHEL or another
operating system for Apigee. You can then use the mirror to
add packages even if you installed Apigee on RHEL 8.0 servers.
149245401: LDAP connection pool settings for JNDI configured through the
are not reflected, and JNDI defaults cause single-use connections each time.
As a result, connections are being opened
and closed each time for single use, creating a large number of
connections per hour to the LDAP server.
In order to change the LDAP connection pool properties, do
the following steps to set a global change across all LDAP policies.
Create a configuration properties file if it does not already exist:
Make sure the file
owned by apigee:apigee.
Restart each message processor.
To verify that your connection pool JNDI
properties are taking effect, you can
perform a tcpdump to observe the behavior of the LDAP connection pool
High Request Processing Latency
139051927: High proxy processing latencies found in the Message Processor
all API Proxies. Symptoms include 200-300ms delays in processing times over normal
times and can occur randomly even with low TPS. This can occur when than more than 50 target
servers in which a message processor makes connections.
Message processors keep a cache that maps target server URL to HTTPClient object for
outgoing connections to target servers. By default this setting is set to 50 which may be
too low for most deployments. When a deployment has multiple org/env combinations in a setup,
and have a large number of target servers that exceed 50 altogether, the target server URLs
keep getting evicted from cache, causing latencies.
To determine if target server URL eviction is causing the latency problem, search the
Message Processor system.logs
for keyword "onEvict" or "Eviction". Their presence in the logs indicate that target server URLs
are getting evicted from the HTTPClient cache because the cache size is too small.
For Edge for Private Cloud versions 19.01 and 19.06, you can edit and configure the HTTPClient
Then restart the message processor. Make the same changes for all message processors.
The value 500 is an example. The optimal value for your setup should be greater than
the number of target servers that the message processor would connect to. There are no side
setting this property higher, and the only affect would be an improved message processor
proxy request processing times.
Note: Edge for Private Cloud version 50.00 has the default setting of 500.
Multiple entries for key value maps
157933959: Concurrent inserts and updates to the same key value map (KVM) scoped to the
organization or environment level causes inconsistent data and lost updates.
Note: This limitation only applies to Edge for Private Cloud. Edge for Public Cloud
and Hybrid do not have this limitation.
For a workaround in Edge for Private Cloud, create the KVM at the