SOA-P cluster on MySQL fails with 'Too many open connections'

Solution Verified - Updated -

Environment

  • JBoss Enterprise SOA Platform (SOA-P) 5.3.1
  • Cluster, running with MySQL

Issue

One SOA-P instance can be started with a MySQL database, but when a second node is started it fails with messages about 'Too many open connections'. What can be done?

Resolution

  • Make sure there are no custom applications leaking connections
  • Determine the number of connections used by our datasources
$ grep -rn 'min-pool-size' $SOA_HOME/jboss-as/server/$YOUR_PROFILE/deploy
  • Compare this sum to the number of connections the database allows. The database should have a facility for doing this.
  • Finally, decide if we want to increase the number of connections the database will allow (the database should have a facility for this) or if we want to trim SOA-P or it's component's connection usage. Make either adjustment, this should cure the problem.

Root Cause

Too many connections are being requested from the database.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments