Popular Posts

Friday, February 28, 2014

Common mistakes to avoid in WSO2 Carbon - 2 - "java.sql.SQLException: Total number of available connections are less than the total number of closed connections"

This is the second post of common mistakes blog series which I'm planning to share with you. In this post, we are looking into another common mistake which we do when working with WSO2 Carbon platform.

Registry mounting is a way of federating the registry space across multiple servers in a product cluster. For example, if you have a WSO2 ESB cluster, you can use a single registry space to store all configuration data common to cluster nodes.
There are 3 different registry spaces provided by each WSO2 Carbon product; local, configuration and governance. You can find more details about these spaces in here.

We have to keep in mind a few important concepts when building a shared registry setup. You cannot share the local registry space among multiple cluster nodes. The local registry space is used to store node-specific data hence it should not be shared among other nodes in the cluster. However, we mistakenly do this when configuring shared registry setups and experience many unexpected issues. The following weird startup error is one such occurrence due to incorrect mounting configurations (I removed some part of the complete stack trace for clarity).

ERROR - RegistryCoreServiceComponent Failed to activate Registry Core bundle
org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to close transaction.
    at org.wso2.carbon.registry.core.jdbc.dataaccess.JDBCTransactionManager.endTransaction(JDBCTransactionManager.java:183)

Caused by: java.sql.SQLException: Total number of available connections are less than the total number of closed connections
    at org.wso2.carbon.registry.core.jdbc.dataaccess.JDBCDatabaseTransaction$ManagedRegistryConnection.close(JDBCDatabaseTransaction.java:1349)
    at org.wso2.carbon.registry.core.jdbc.dataaccess.JDBCTransactionManager.endTransaction(JDBCTransactionManager.java:178)

This error does not give any clue about a problem related to mounting. You may have spent many hours unnecessarily to tune up your DBMS since the error says about DB connections! 

Let's explore this error in detail.

Step 1


We are going to have a shared registry database (which is used as configuration and governance registry spaces in a ESB cluster). I will use mySQL and create a database first.

mysql> create database sharedreg_db;

Next, create the registry DB schema using mySQL database scripts available in CARBON_HOME/dbscripts directory.

mysql> use sharedreg_db;
mysql> source /home/charitha/products/esb/tmp/wso2esb-4.8.1/dbscripts/mysql.sql;

Step 2


We will register this new database in master-datasources.xml which can be found at
CARBON_HOME/repository/conf/datasources directory

            <description>The datasource used for shared registry</description>
            <definition type="RDBMS">
                    <validationQuery>SELECT 1</validationQuery>

Step 3


Now, we have a shared registry database. We need to mount the registry collections to this remote database. There are 3 mounting mechanisms; JDBC, Atom and WS. The commonly used pattern is JDBC mounting. Hence I will use the same.
Mounting configuration can be done in CARBON_HOME/repository/conf/registry.xml as shown below.

<remoteInstance url="https://localhost:9443/registry">







    <mount path="/_system/config" overwrite="true">



    <mount path="/_system/governance" overwrite="true">




Make a note of the highlighted configuration parameter.

Now, the database configuration referred by the mount is defined at the top of registry.xml as follows.
We simply change the JNDI name of the default db config; jdbc/WSO2CarbonDB to the JNDI name of our shared registry database; jdbc/WSO2SharedRegDB





    <dbConfig name="wso2registry">



OK. Assuming everything is configured correctly, we start Carbon server. Unfortunately, you will get the above meaningless error at the server startup.

What is wrong here?


By defining a common data source for mount configuration as well as local registry definition (under currentDBConfig element), we have done a big mistake. This will eventually leads to share local registry space among heterogeneous product cluster nodes which is theoretically incorrect.  

How can we fix this?


Simple. You can define a separate, unique database configuration for the shared registry db.

<dbConfig name="sharedregistry">



Then, that will be referenced by the remote mounting configuration.

<remoteInstance url="https://localhost:9443/registry">







Finally, make sure to change the local registry definition back to its default so that it will use the WSO2 Carbon DB (usually H2).

<dbConfig name="wso2registry">



Restart the server. The error will disappear!


Wen Andes said...

Hi, great to see the explaination of this error that I simply got today. But in my scenario, I have two AS nodes mounting to the same default local DB. In my opinion, we can use a local registry in one node, and mount another node to the previous one. Theoretically, they are the some production. But why not?

Ase Rety said...


if we use a diferrent registryRoot for each node, for example:

/instance1 for instante 1 and /instance2 for instance 2. in this scenario,

Is it posibble to share the same local database between the two ESB nodes?.


Harshana Martin said...

Hi Charitha,

This is an extremely useful post and a very common mistake most people do when they perform the Remote Registry configuration.

May be a good idea to include this in FAQ of the Documentation guide.

Thanks and Regards,

Susinda Perera said...

Hi Charitha Ayya

What a great post..

Thanks for sharing.


Ruli said...

Finally.. you save my week !!!!

Official doc is a bit confusing..