Oc4j connection pool: too much INACTIVE connections

Question

I am publishing an application - developed using Eclipse and previously published in Tomcat (where it works perfectly for a long time) - within corporate servers using Oc4j version 10.1.3. The database server is Oracle 9g.
After the deployment operation, the application seems to work, but that happens during the work by users, there are still many connections whith status "INACTIVE", until to complete all the available connections.
The datasource is set as follows:
<connection-pool name="ConnectionPoolRichiestaPubblicazione">
<connection-factory factory-class="oracle.jdbc.pool.OracleDataSource"
user="REDAZIONE"
password="password"
url="jdbc:oracle:thin:@(DESCRIPTION=(FAILOVER=ON)
     (ADDRESS_LIST=(LOAD_BALANCE=ON)
     (ADDRESS=(PROTOCOL=TCP)
     (HOST=10.146.2.86)(PORT=1521))
     (ADDRESS=(PROTOCOL=TCP)(HOST=10.146.2.86)(PORT=1521)))
     (CONNECT_DATA=
(SERVER=DEDICATED)
(SERVICE_NAME=XE)
(FAILOVER_MODE=(TYPE=SELECT)(METHOD=BASIC)(RETRIES=180)(DELAY=5))))">
</connection-factory>
</connection-pool>
<managed-data-source
jndi-name="jdbc/RichiestaPubblicazioneDS"
name="RichiestaPubblicazioneDS"
connection-pool-name="ConnectionPoolRichiestaPubblicazione" />
The java code to establish a connection is as follows:
private Connection creaConnessioneDataSource(String nomedatasource) throws ConnessioneException{
          LOGGER.debug("START");
          try {
               InitialContext context = new InitialContext();
               DataSource ds = (DataSource)context.lookup(nomedatasource);
               LOGGER.debug("URL DATASOURCE : " + ds.getConnection().getMetaData().getURL());
               LOGGER.debug("USERNAME : " + ds.getConnection().getMetaData().getUserName());
               this.conn = ds.getConnection();
          catch( Exception e ) {
               LOGGER.error("Errore nella connessione tramite datasource : " + StringUtils.getCustomStackTrace(e));
          LOGGER.debug("END");
          return this.conn;
Connections and statements are closed using the following methods:
     public boolean chiudi(Connection conn){
          LOGGER.debug("START");
          boolean esito = false;
          if (conn != null){
               try {
                    conn.close();
                    esito = true;
                    LOGGER.debug("Connessione chiusa");
               catch (SQLException e) {
                    LOGGER.error("Eccezione nella chiusura della connessione : " + e);
          LOGGER.debug("END");
          return esito;
     public boolean chiudi(Statement stmt){
          LOGGER.debug("START");
          boolean esito = false;
          if (stmt != null){
               try {
                    stmt.close();
                    esito = true;
                    LOGGER.debug("Statement chiuso");
               } catch (SQLException e) {
                    LOGGER.error("Eccezione nella chiusura dello statement : " + e);
                    e.printStackTrace();
          LOGGER.debug("END");
          return esito;
Here are a couple of examples of code that interact with the database:
     public List<StatoRichiestaSintesi> getElencoStatiRichieste() throws ConnessioneException{
          LOGGER.debug("START");
          List<StatoRichiestaSintesi> listaStati=new LinkedList<StatoRichiestaSintesi>();
          LOGGER.debug("Apriamo connessione e statement");
          Connection conn = databaseManager.creaConnessioneDataSource(datasource);
          Statement stmt = databaseManager.creaStatement(conn, false);
          String sql="SELECT * FROM STATORICHIESTA";
          try {
               ResultSet rs = stmt.executeQuery(sql);
               while(rs.next()){
                    StatoRichiestaSintesi temp=new StatoRichiestaSintesi();
                    temp.setIdStato(rs.getString(1));
                    temp.setDescrizioneStato(rs.getString(2));
                    listaStati.add(temp);
               LOGGER.debug("Numero record trovati : " + listaStati.size());
          } catch (SQLException e) {
               LOGGER.error("Eccezione di tipo SQL : " + StringUtils.getCustomStackTrace(e));
          finally{
               LOGGER.debug("Chiusura di statement e connessione");
               databaseManager.chiudi(stmt);
               databaseManager.chiudi(conn);
          LOGGER.debug("END");
          return listaStati;
Below is another example using PreparedStatement:
     private synchronized void aggiungiIndicazioneProgetto(String idprogetto, String idrichiesta) {
          LOGGER.debug("START");
          LOGGER.debug("Creo un oggetto di tipo connessione");
          Connection conn = databaseManager.creaConnessioneDataSource(datasource);
          LOGGER.debug("Definisco una query sql");
          String sql = "INSERT INTO RICHIESTAPROGETTO (IDRICHIESTA,IDPROGETTO) VALUES (?,?)";
          LOGGER.debug("Dichiaro un oggetto di tipo preparedstatement");
          PreparedStatement stmt = null;
          try {
               LOGGER.debug("Istanzio l'oggetto statement");
               stmt = conn.prepareStatement(sql);
               LOGGER.debug("Imposto i segnalibri della query");
               stmt.setString(1, idrichiesta);
               stmt.setString(2, idprogetto);
               LOGGER.debug("Eseguo la query di inserimento del progetto");
               stmt.executeUpdate();
          } catch (SQLException e) {
               LOGGER.error("Eccezione di tipo SQL : " + StringUtils.getCustomStackTrace(e));
          finally {
               LOGGER.debug("Chiusura di statement e connessione");
               databaseManager.chiudi(stmt);
               databaseManager.chiudi(conn);
          LOGGER.debug("END");
     Which may be the cause for the described behavior?
     I hope someone help me..

Answer 1

My problem is the following.
If I deploy my application with the illustred datasource in my local OC4J (10.1.3 in a Standalone Environment) all work fine.
The application creates a reasonable number of connections (in ORACLE - 10g Enterprise Edition Release 10.2.0.4.0 - db I run the query verification "select count(*) from v$session where username='MYAPPLICATION'"), and overall performance is very good.
If, however, to deploy on the production machine of corporate (always 10.1.3, but obviously in Oracle Application Server Environment) the
number of connections (status 'INACTIVE') grows massively, and this is saturated in a short time.
The exception that at the end from the application is that:
java.sql.SQLException: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:138)
oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)
oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:277)
oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:272)
oracle.jdbc.driver.T4CTTIoauthenticate.receiveOsesskey(T4CTTIoauthenticate.java:243)
oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:304)
oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:430)
oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:151)
oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:608)
oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:218)
oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:114)
oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:77)
oracle.jdbc.pool.OracleImplicitConnectionCache.makeCacheConnection(OracleImplicitConnectionCache.java:1361)
oracle.jdbc.pool.OracleImplicitConnectionCache.getCacheConnection(OracleImplicitConnectionCache.java:441)
oracle.jdbc.pool.OracleImplicitConnectionCache.getConnection(OracleImplicitConnectionCache.java:336)
oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:286)
oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:179)
oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:159)
oracle.oc4j.sql.DataSourceConnectionPoolDataSource.getPooledConnection(DataSourceConnectionPoolDataSource.java:57)
oracle.oc4j.sql.xa.EmulatedXADataSource.getXAConnection(EmulatedXADataSource.java:92)
oracle.oc4j.sql.spi.ManagedConnectionFactoryImpl.createXAConnection(ManagedConnectionFactoryImpl.java:211)
oracle.oc4j.sql.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:170)
com.evermind.server.connector.ApplicationConnectionManager.createManagedConnection(ApplicationConnectionManager.java:1377)
oracle.j2ee.connector.ConnectionPoolImpl.createManagedConnectionFromFactory(ConnectionPoolImpl.java:327)
oracle.j2ee.connector.ConnectionPoolImpl.access$800(ConnectionPoolImpl.java:98)
also I add the other attributes of Connection Pool of the Datasource:
Connections:
Initial size of Connection Cache = 0     
Minimum Number of Connections = 0
Maximum Number of Connections = -1
Connection Retry Interval (seconds) = 1
Maximum Connection Attempts = 3
Maximum Number of Statements Cached = 0     
Lower Threshold Limit On Pool (%)= 20     
Validate Connection = False
What I can do?
many thanks..