Skip to main content
Support

KB Article #180127

No API Manager runtime cache - cannot process request

Problem

An error like the following is observed in API Manager:


DEBUG    01.01.01 00:00:00.000    No API Manager runtime cache - cannot process request
ERROR    01.01.01 00:00:00.000    Filter that caused failure: Error 
Policy 'API Broker' {
    Filter 'Error' Status:  FAILED
}
Error filter failed

Resolution

This may happen due to JAR conflicts implicating the VAPI cache JARs. Check /apigateway/ext/lib/ for any patches that do not belong to the gateway version you are running. These may be conflicting with your version and you can fix that by removing the JAR files and restart. You may find further information on the JARs in /apigateway/META-INF/ in the text files with the .id extension. If no conflicting patches are found, reapply the current SP, making sure to carefully follow the prerequisites section of the release notes which have you delete several directories containing potentially conflicting JARs.