Jitterbit · Private agents

Agent is incapable to process this message

Short answer

This Jitterbit ProcessEngine.log message means the agent has no free capacity, because every worker thread is in use or a capability metric reached its threshold. Review ProcessEngine.log for repeated capability status changes.

VerifiedLast verified

01Error text

Jitterbit error
Agent (Id: ...) is incapable to process this message. Message will be auto-retried.
Capability status changed from true to false

02Likely causes

  • Every worker thread in the process engine is in use.
  • An optional capability metric (CPU, memory or Apache thread usage) is enabled and has reached its threshold.
  • A single agent in the group handles more load than it can sustain while others are idle.

03How to fix it

  1. Review ProcessEngine.log for repeated capability status changes.
  2. If many operations run at once, consider a conservative increase in MaxNumberOfWorkerThreads.
  3. Check which metrics are enabled in [AgentCapability] and the host CPU and memory at the time of the issue.
  4. If limits are consistently reached, add agents to the group.

04Official documentation

Test every fix in a non-production environment before you apply it to production. See how entries are verified.

More for Jitterbit work:Open Jitterbit jobsJitterbit rates and salaries

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.