OSB: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool wlsbjmsrpDataSource

(Doc ID 1636384.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle Service Bus - Version 2.1 and later
Information in this document applies to any platform.

Symptoms

After upgrading OSB Project from 10.3.1 to 11.1.1.7, you created a domain and the OSB reporting tables manually.

When some error occurs (e.g. some configuration error with the table), you found that, except the normal error with the wrong configuration, all the jdbc connections were used up in wlsbjmsrpDataSource pool and the error was:

<Jan 23, 2014 4:36:22 PM CST> <Error> <OSB-Reporting> <P570_P12_tmp> <server1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <BEA1-031CDC5775BE9E3C13A0> <ce5d5cb6d327b70b:5b2ab32d:143be341523:-8000-0000000000000138> <1390466182251> <BEA-473514> <An unexpected error occurred while receiving the message in ReportingMDB javax.ejb.EJBException: [OSB-Reporting:473520]An error occurred while initializing the ReportingMDB and Database details.; nested exception is: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool wlsbjmsrpDataSource to allocate to applications, please increase the size of the pool and retry..
javax.ejb.EJBException: [OSB-Reporting:473520]An error occurred while initializing the ReportingMDB and Database details.; nested exception is: weblogic.jdbc.extensions.PoolLimitSQLException: weblogic.common.resourcepool.ResourceLimitException: No resources currently available in pool wlsbjmsrpDataSource to allocate to applications, please increase the size of the pool and retry..
    at com.bea.wli.reporting.jmsprovider.runtime.ReportingMDB.getDbandConInfo(ReportingMDB.java:199)
    at com.bea.wli.reporting.jmsprovider.runtime.ReportingMDB.__onMessage(ReportingMDB.java:111)
    at com.bea.wli.reporting.jmsprovider.runtime.ReportingMDB.access$000(ReportingMDB.java:43)
    at com.bea.wli.reporting.jmsprovider.runtime.ReportingMDB$1.run(ReportingMDB.java:98)
    at com.bea.wli.reporting.jmsprovider.runtime.ReportingMDB$1.run(ReportingMDB.java:96)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.security.Security.runAs(Security.java:41)
    at com.bea.wli.reporting.jmsprovider.runtime.ReportingMDB.onMessage(ReportingMDB.java:96)
    at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:518)
    at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:486)
    at weblogic.ejb.container.internal.NewJMSMessagePoller.processOneMessage(NewJMSMessagePoller.java:282)
    at weblogic.ejb.container.internal.NewJMSMessagePoller.run(NewJMSMessagePoller.java:120)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:531)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:252)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms