Java Callouts runtime limits

[brendanvu]

Hi,

We would like to use Java Callouts in our policies but we need to have some information about specs and limits.

We'd like to know the following Java runtime details:
- CPU
- RAM
- ThreadPool associated
And we'd like to know how those limit are enforced (at org level, or Proxy level).

Thanks in advance.

[adevegowda · Accepted solution]

@Brendan

Any policy within Edge including Java Callouts gets executed within Message Processor component. If you are using Private Cloud, then you can refer to Hardware requirements to know about the minimum hardware requirements for CPU, RAM, Hard disk space for Message Processor and the other Edge components as well.

Of course depending on the traffic volume, kind of operations being performed by different policies in your API Proxies, you may require fewer or more resources.

Message Processor serves traffic for all the API Proxies deployed on one or more environments in an organization. Therefore, the usage of resources (CPU, Memory, thread pool etc) will be effected by the traffic pattern and operations performed by all the API Proxies in the specific environments/organization supported by the Message Processor.

If you are using Public Cloud, all the above things holds good except for the fact that Apigee manages the infrastructure and hardware requirements based on traffic volume information provided by you.