WSO2 API Manager - Sharing registry

Question

I'm following this documentation set: http://wso2.com/library/tutorials/2010/04/sharing-registry-space-across-multiple-product-instances/#CO_JDBC

I currently have 3 DBs: User, Registry, and API per the API Manager documentation. I have things configured as noted with the exception of having a cluster.

    <!--for store and publisher only-->
    <dbConfig name="govregistry">
        <dataSource>jdbc/WSO2REG_DB</dataSource>
    </dbConfig>
    <remoteInstance url="https://localhost:9447/registry">
        <id>gov</id>
        <dbConfig>govregistry</dbConfig>
        <readOnly>false</readOnly>
        <enableCache>true</enableCache>
        <registryRoot>/</registryRoot>
    </remoteInstance>
    <mount path="/_system/governance" overwrite="true">
        <instanceId>gov</instanceId>
        <targetPath>/_system/governance</targetPath>
    </mount>

I have one server for store (on port 9447), and publisher (on port 9446) as well as a different server for gateway (port 9445), and key manager (port 9444) but continually get the following when starting the store or publisher (the WSO2 doc for API Manager:http://docs.wso2.org/display/CLUSTER420/Clustering+API+Manager did NOT say I should create entries for those items in the regsitry.xml file).

TID: [0] [AM] [2014-01-22 17:26:30,409] ERROR {org.wso2.carbon.governance.api.util.GovernanceUtils} - Error in getting the path from the registry. Execute query failed with message : PooledConnection has already been closed. {org.wso2.carbon.governance.api.util.GovernanceUtils}

Should I have created a whole new seperate DB instance for the shared config/governance, or should I be reusing the existing Registry DB? Stabbing in the dark as to why the connection pool is already closed...

Noted that the following doc: docs.wso2.org/display/Governance460/… says that the DBconfig should not be the default config. In my case, when following WSo2 API Manager documentation the carbon DB config points to the REG_DB, and then we make another entry that points to REG_DB. That would seem to indicate that I should have a REG_DB and another Shared_REG_DB...but the documentation is not clear on if it means 2 different DB's or just different DBConfigs. — Gammonster

Nadeesha Nadeesha · Accepted Answer · 2014-01-23T17:28:44

You need to share your gov and config registry among the instances of the API Manager. Add a new entry in the Registry.xml for this. I recommend you to use a standalone DB to mount the gov and config registry.

WSO2 API Manager - Sharing registry

2 Answers