My Oracle Support Banner

JCAPS Master Index Outbound JMS Error: Cannot allocate more connections (Doc ID 1493272.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Java CAPS Enterprise Service Bus - Version R6.2 and later
Information in this document applies to any platform.
***Checked for relevance on 02-April-2014***


We have a JCAPS Master Index Application that uses a topic to distribute outbound match information.
The updates to the master index are received via a webservice which calls the executeMatch method on the master index app.

After the app has been running for a few days, it starts complaining that it is unable to create a topic connection because it has reached the max-pool-size and the max-wait-time has expired.

The jms settings for the JMSDestination in the master index connectivity map are:
Transaction Mode: Transacted
Delivery mode: Persistent
Priority: 4
Idle Timeout: 30
Maximum Wait Time: 30000
Maximum Pool Size: 32
Steady Pool Size: 4

Increase the Max Pool size and decrease the Idle Timeout seems does not help.

The exception in the app server logs is:

#|2012-09-13T09:14:59.886+0800|WARNING|sun-appserver2.1|javax.enterprise.resource.resourceadapter|_ThreadID=112;_ThreadName=p: thread-pool-1; w: 79;ParentMasterIndex#ParentMasterIndexSvc_ParentMatchOutputTopic#javax.jms.TopicConnectionFactory;In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.;_RequestID=01e2b35b-be3d-4ac1-aeb9-76f61322e6aa;|RAR5117 : Failed to obtain/create connection from connection pool [ ParentMasterIndex#ParentMasterIndexSvc_ParentMatchOutputTopic#javax.jms.TopicConnectionFactory ]. Reason : In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.|#]

[#|2012-09-13T09:14:59.886+0800|SEVERE|sun-appserver2.1||_ThreadID=112;_ThreadName=p: thread-pool-1; w: 79;_RequestID=01e2b35b-be3d-4ac1-aeb9-76f61322e6aa;|Exception Failed to establish a topic connection: JMSJCA-E034: Could not create session javax.jms.TopicSession: Error in allocating a connection. Cause: In-use connections equal max-pool-size and expired max-wait-time. Cannot allocate more connections.
at sun.reflect.GeneratedMethodAccessor4165.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at com.sun.ejb.containers.interceptors.BeanCallbackInterceptor.intercept(
at com.sun.ejb.containers.interceptors.CallbackChainImpl.invokeNext(
at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(
at com.sun.ejb.containers.StatelessSessionContainer.createStatelessEJB(
at com.sun.ejb.containers.StatelessSessionContainer.access$100(
at com.sun.ejb.containers.StatelessSessionContainer$SessionContextFactory.create(
at com.sun.ejb.containers.util.pool.NonBlockingPool.preload(
at com.sun.ejb.containers.util.pool.NonBlockingPool.doResize(
at com.sun.ejb.containers.util.pool.NonBlockingPool$
at com.sun.ejb.containers.util.pool.NonBlockingPool$ReSizeWork.service(
at com.sun.ejb.containers.util.WorkAdapter.doWork(



To view full details, sign in with your My Oracle Support account.

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

In this Document

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.