Hi Prayang,
The datasources configured are correct. I assume you configure same URL,
username, password for local and container setup when you say "The same
configurations work fine when we run locally but fails when we deploy the
same in docker."

If that is the case, these two cases need to be looked at.
1) connectivity may be slow or intermittent form container to your DB server
2) your container is given very low effective core count

Cheers,
Ruwan

On Thu, Jul 23, 2020 at 9:42 AM prayag pavithran <
[email protected]> wrote:

> Thanks Ruwan.
>
> Currently in deployment.toml file we've configured the mysql connection
> strings for
>
>    1. [database.identity_db]
>    2. [database.shared_db]
>
> Could you please let me know if any other configuration need to be done in
> deplyment.toml file for pointing to mysql database (for User and Identity)
> instead of default H2 database.
> The same configurations work fine when we run locally but fails when we
> deploy the same in docker.
>
> Any help on this will be much appreciated.
>
> Thanks & Regards,
> Prayag Pavithran
>
> ------------------------------
> *From:* Ruwan Abeykoon <[email protected]>
> *Sent:* Thursday, July 23, 2020 6:12 AM
> *To:* prayag pavithran <[email protected]>
> *Cc:* WSO2 Developers' List <[email protected]>
> *Subject:* Re: [Dev] Help required for fixing error when running wso2
> 5.10.0 in docker container
>
> Hi @prayag pavithran <[email protected]> ,
> The following error on the stack trace,
> " Pool empty. Unable to fetch a connection in 30 seconds, none
> available[size:100; busy:100; idle:0; lastwait:30000]."
>
> This suggests that some queries take too much time to complete in the
> containerized environment. You should be able to find out why this happens
> on your DB side by looking at the slow query logs.
>
> One possibility is that you are still using the internal H2 database(for
> User and Identity), and your container is having low core count available
> for database operations.
>
> Cheers,
> Ruwan A
>
> On Thu, Jul 23, 2020 at 12:53 AM prayag pavithran <
> [email protected]> wrote:
>
> Hi ,
>
> When running wso2 5.10.0 inside docker container , we are getting the
> following error
>
> TID: [-1234] [] [2020-07-22 18:51:46,513] [] ERROR
> {org.wso2.carbon.idp.mgt} - [SCR] Error while trying to bind reference
> Reference[name = identity.core.ConnectorConfig, interface =
> org.wso2.carbon.identity.core.ConnectorConfig, policy = dynamic,
> cardinality = 0..n, target = null, bind = setIdentityGovernanceConnector,
> unbind = unsetGovernanceConnector]
> Details:
> Problematic reference = Reference[name = identity.core.ConnectorConfig,
> interface = org.wso2.carbon.identity.core.ConnectorConfig, policy =
> dynamic, cardinality = 0..n, target = null, bind =
> setIdentityGovernanceConnector, unbind = unsetGovernanceConnector]
> of service component = idp.mgt.dscomponent
> component implementation class =
> org.wso2.carbon.idp.mgt.internal.IdPManagementServiceComponent
> located in bundle with symbolic name = org.wso2.carbon.idp.mgt
> bundle location =
> reference:file:../plugins/org.wso2.carbon.idp.mgt_5.17.5.jar
> java.lang.reflect.InvocationTargetException
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:376)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:444)
>
> Caused by: org.wso2.carbon.identity.base.IdentityRuntimeException:
> org.apache.tomcat.jdbc.pool.PoolExhaustedException: [Framework Event
> Dispatcher: Equinox Container: a9c9b7c1-ff59-47c7-a072-e463cbe8c8e2]
> Timeout: Pool empty. Unable to fetch a connection in 30 seconds, none
> available[size:100; busy:100; idle:0; lastwait:30000].
> at
> org.wso2.carbon.identity.base.IdentityRuntimeException.error(IdentityRuntimeException.java:71)
> at
> org.wso2.carbon.identity.core.persistence.JDBCPersistenceManager.getDBConnection(JDBCPersistenceManager.java:166)
> at
> org.wso2.carbon.identity.core.util.IdentityDatabaseUtil.getDBConnection(IdentityDatabaseUtil.java:54)
> at
> org.wso2.carbon.idp.mgt.dao.IdPManagementDAO.getIDP(IdPManagementDAO.java:1541)
> at
> org.wso2.carbon.idp.mgt.dao.IdPManagementDAO.getIdPByName(IdPManagementDAO.java:1488)
> at
> org.wso2.carbon.idp.mgt.dao.CacheBackedIdPMgtDAO.getIdPByName(CacheBackedIdPMgtDAO.java:158)
> at
> org.wso2.carbon.idp.mgt.IdentityProviderManager.getResidentIdP(IdentityProviderManager.java:324)
>
> With the same configurations wso2 is runs fine locally . Could you please
> help me in solving the above said issue in docker.
>
>
> Thanks & Regards,
> Prayag Pavithran
>
>
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>
> --
> Ruwan Abeykoon | Director/Architect | WSO2 Inc.
> (w) +947435800  | Email: [email protected]
>
>

-- 
Ruwan Abeykoon | Director/Architect | WSO2 Inc.
(w) +947435800  | Email: [email protected]
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to