What causes constant network traffic between JBoss SOA-P 4.x and the database?

Solution Verified - Updated -



  • Starting the default server leads to almost constant network communication from JBoss SOA-P to the database.
  • There is an awfully large amount of network traffic going back and forth between our JBoss SOA-P node and JON node.
  • Constant network traffic between JON Agent and the database, even without any custom esb applications deployed and no clients accessing the JBoss SOA platform.
  • It seems as though it's the JON agent and the database sending each other several UDP packets per second on one of our configurations and on another configuration, the jboss-esb data store and the database are sending these packets back and forth.
  • Database size increases very quickly.
  • The JMX* tables, in particular the JMXDATA table, is increasing rapidly and causes the start time of the server to increase.
  • After several days the JBoss ESB database reached 2.4 GB size.  Why is such a great amount of data written to the database? Is it possible to tune/avoid this massive data store?
  • Too many DB connections opened by JBoss.


  • JBoss Enterprise SOA Platform (SOA-P)
    • 4.2.x
    • 4.3.x
  • JBoss Operations Network (JON)


Remove the management.esb console:

  1. Remove management.esb from $JBOSS_HOME/server/<config>/deploy/

  2. Remove management-ds.xml from $JBOSS_HOME/server/<config>/deploy/

  3. Delete the link to the Management Console $JBOSS_HOME/server/<config>/deploy/jboss-web.deployer/ROOT.war/index.html:

    • <!-- <li><a href="/jbossesb/" target="_blank">JBossESB Management Console</a></li> -->
  4. Remove the management services and queues from the $JBOSS_HOME/server/<config>/deploy/jbossesb.esb/META-INF/jboss-esb.xml

    • Remove these services: InvokerService, OperationsCollectorService, DataCollectorService

    • Remove the corresponding queues: DataCollector, OperationsCollector, OperationsStatusCollector

  5. Clear out the database so juddi will not be requesting the EPRs to monitor.  Specifically, DROP the following tables from the database:  


Root Cause

The management.esb console application is known to cause too much network traffic, and too many database entries. It has thus been removed from SOA-P in version 5.x. For monitoring, using JBoss ON is recommended [1].

Diagnostic steps

  • Verify if management.esb is installed in the SOA-P instance.
  • Check server.log file of the SOA-P instance.
  • Check datasource configuration files of the SOA-P instance.
  • Verify if the JON agent can ruled out as the cause.

[1] http://www.jboss.com/products/jbosson/

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content