PO Is Stuck

(Doc ID 2371877.1)

Last updated on MARCH 13, 2018

Applies to:

Oracle SOA Suite - Version 11.1.1.7.8 and later
Information in this document applies to any platform.

Symptoms

On : 11.1.1.7.8 version, B2B Engine

After a restart from Network issues, SOA composite is faulting with following message when trying to read messages from the source JMS Queue eis/wls/eb2b

Configured maximum limit of (0) on number of threads allowed to wait for a resource reached for pool eis/wls/eb2b

ERROR
-----------------------
[2018-01-05T08:16:38.347-07:00] [eb2b_soa4] [WARNING] [] [oracle.soa.adapter] [tid: DaemonWorkThread: '96' of WorkManager: 'wm/SOAWorkManager'] [userId: ] [ecid: 0000M36NOqP56iMCEN6iKw1QJrE800000h,0] [APP: soa-infra] JMSAdapter Custom8944010UCSDRInboundXfmService JMSMessageConsumer_init:[destination = EB2BJMSServer1@jms/eb2bB2BSoa894BDR4010UCS (payload = 1)]: Retrying connection; attempt #14
[2018-01-05T08:16:38.358-07:00] [eb2b_soa4] [WARNING] [] [oracle.soa.adapter] [tid: DaemonWorkThread: '96' of WorkManager: 'wm/SOAWorkManager'] [userId: ] [ecid: 0000M36NOqP56iMCEN6iKw1QJrE800000h,0] [APP: soa-infra] JMSAdapter Custom8944010UCSDRInboundXfmService [[
javax.resource.spi.ApplicationServerInternalException: Unable to get a connection for pool = 'eis/wls/eb2b', weblogic.common.resourcepool.ResourceLimitException: Configured maximum limit of (0) on number of threads allowed to wait for a resource reached for pool eis/wls/eb2b
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:449)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:341)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:131)
at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:93)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:320)
at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:921)
at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:947)
at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:1135)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: weblogic.common.resourcepool.ResourceLimitException: Configured maximum limit of (0) on number of threads allowed to wait for a resource reached for pool eis/wls/eb2b
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:541)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:352)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:668)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:326)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:407)
... 10 more

]]


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, composite is not picking messages to be sent to B2B

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