If there is a value set in the API_METHOD parameter of the "Capture Identity of Requestor" assertion in any policies used by API Developer Portal, it can cause some of the following symptoms:
- high disk I/O
- MySQL server may stop writing to the database if the disk is full
- the "service_metrics" table may grow much more frequently than expected
- replication may break between MySQL servers (if replicated)
Note: The symptoms will specifically occur on the CA API Gateway, not the CA Developer Portal. However, this issue has (so far) only been seen when both the CA API Gateway and CA Developer Portal are integrated together, along with a value set for API_METHOD instead of kept at the default value of empty.