Performance issues when jBPM uses EsbActionHandler to call ESB service

Solution In Progress - Updated -


In our SOA-P environment, we are using jBPM to orchestrate ESB service execution. Sometimes we see that the process execution is taking a long time, eg. we had a process instance taking 85 seconds to complete.

We took a deeper look at the execution of a process instance, in particular at the transition from one ESB node to another. The node just contains an EsbActionHandler, calling an ESB dummy service for testing purposes. This ESB service just has one action to just output the ESB message. This node took 5 whole seconds to transition to the next node.

  • Why is it taking so long to execute a node with an EsbActionHandler, before the token proceeds to the next node?
  • As we have seen this happening mainly under high load, are there any potential bottlenecks, where further tuning actions could be applied?


  • JBoss Enterprise SOA Platform (SOA-P)
    • 4.x
    • 5.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In