When would applications receive the following exception: “javax.jms.ResourceAllocationException: too many open connections”?
Article ID: KB0084583
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Description
===========
“javax.jms.ResourceAllocationException: too many open connections”
Environment
==========
All
Causes
======
There are two possible reasons for this error:
1). You have set max_connections to a non-zero value in the tibemsd.conf file and the number of normal client connections for your EMS server has already reached this value. Here, a normal client is either a producer or a consumer of your business messages which connects to the EMS server on the port EMS opens for client connections.
Look for number of connections for whose value under ‘T’ in FSXT (Connection type information) in the show connections output is either ‘C’, ‘T’ or ‘Q’, and compare this to your max_connections setting (if any).
2). The number of programmatic admin connections to this server reaches 256. Programmatic admin connections (combination of .net admin API and java admin API clients) are limited to 256 maximum connections. The tibemsadmin tool and all other connections (FT and route) are unlimited.
Look for number of connections for whose value under ‘T’ in FSXT (Connection type information) in the show connections output is ‘A’ and the value under heading ‘L’ (type of client) is not ‘C’.
Description
===========
“javax.jms.ResourceAllocationException: too many open connections”
Environment
==========
All
Causes
======
There are two possible reasons for this error:
1). You have set max_connections to a non-zero value in the tibemsd.conf file and the number of normal client connections for your EMS server has already reached this value. Here, a normal client is either a producer or a consumer of your business messages which connects to the EMS server on the port EMS opens for client connections.
Look for number of connections for whose value under ‘T’ in FSXT (Connection type information) in the show connections output is either ‘C’, ‘T’ or ‘Q’, and compare this to your max_connections setting (if any).
2). The number of programmatic admin connections to this server reaches 256. Programmatic admin connections (combination of .net admin API and java admin API clients) are limited to 256 maximum connections. The tibemsadmin tool and all other connections (FT and route) are unlimited.
Look for number of connections for whose value under ‘T’ in FSXT (Connection type information) in the show connections output is ‘A’ and the value under heading ‘L’ (type of client) is not ‘C’.
Issue/Introduction
When would applications receive the following exception: “javax.jms.ResourceAllocationException: too many open connections”?
Feedback
Yes
No
Powered by
