A CA API Gateway may experience stability and availability issues when the default API Portal Integration Service (or "portalman") is published. An administrator or operator may observe increasingly frequent garbage collection and increases in the amount of used heap space.
Any version of the API Gateway that can interoperate with version 3.0 of the API Developer Portal may be subjected to this issue if the API Portal Integration Service is published. The following article will describe the Gateway versions that are compatible with the appropriate version of the API Developer Portal: API Gateway: Compatibility with the API Developer Portal and Mobile API Gateway
This issue is resolved with an updated service policy. Download the service policy document (portalman-fix-v3.0.xml) attached to this article and execute the following procedure:
The following procedure should succeed if the policy is replaced correctly.
Note: The CMS is accessed via https://gateway.domain.com/admin where "gateway.domain.com" is the fully qualified domain name of the API Developer Portal appliance