App Agent Limits

These limits apply for an App Agent:

• For each node, a maximum of 500 calls per minute. (See dev-mode-suspend-cpm.)
• For each JVM, the maximum heap utilization percentage of 90%. (See heap-storage-monitor-devmode-disable-trigger-pct.)

If a limit is exceeded, an agent log event is generated indicating that the development mode has been turned off because limits were exceeded

Controller Limits

The Controller monitors the number of snapshot segments collected during development monitoring across business transactions. A snapshot segment corresponds to the processing activities for a business transaction on a particular tier. A single business transaction that traverses many tiers can generate more data than several business transactions that only traverse a few tiers.

When the threshold of 5000 snapshot segments per minute is exceeded, the Controller turns off development mode for the top contributing business transactions. The Controller turns off development mode on as many business transactions as are needed to reduce the snapshot segment contribution by 20%.

For example, if a single business transaction is accountable for 25% of the snapshot segments when the threshold is exceeded, only it is turned off. As another example, given the following business transactions and the percentage of snapshot segments, they each contributed when the threshold was exceeded, the first two are turned off:

1. BT1: 17%
2. BT2: 16%
3. BT3: 15%
4. BT4: 15%
5. BT5: 13%
6. BT6: 12%
7. BT7: 12%

You cannot configure this Controller limit.