Problem

When global request or response policies are configured, they are invoked for requests to API Manager on port 8075 and may cause 500 errors.

Resolution

This may happen in particular if a global request policy returns false or aborts, causing the servlet to abort processing and return a 500. This is because the servlet will stop processing the request and return whatever is in content.body if the global policy returns false. There are three ways of dealing with this:

• Ensure the global policy always returns true, or at least always returns true if the inbound port was 8075.
• Do not use a global policy.
• Edit each relative path on port 8075 and remove the checkboxes that instruct the path to call the global policies.