something is killing my message-processor

have few apis on private cloud, something hapend, see 100% cpu usage and whole api return 503 SERVICE_UNAVAILABLE how I can find which api killing my platform ?

1 2 375
2 REPLIES 2

Wow! Sorry to hear that. It's certainly possible that a custom Java callout could include some code that causes the CPU to spin. Have you got custom Java callout policies running?

If this is private cloud, is it possible for you to connect to the MP with a jconsole to see the current running threads, etc?

Former Community Member
Not applicable

Hi @Sebastian Krajewski were there any changes to made to the platform or any new API proxy / policy introduced before this started happening? Maybe a good idea to check the MP logs (<inst-root>/apigee4/var/log/apigee/message-processor) additionally to see if anything else is going on. @Paul Mibus