1) In querys that involves transactions I use daoMgr.StartTransaction and always daoMgr.EndTransaction. But in simple querys like above, Do I need to daoMgr.EndTransation?

try{
            adStandardDAO = (AdStandardDAO) daoMgr.getDao(AdStandardDAO.class);
            return adStandardDAO.selectAdStandards();
        }
        catch(DaoException e)
        {
            throw new ServiceException(e);
        }

2) have you tried playing with maxRequests in <settings>?
No, should I do this in SQL-MAP-Config ?

3) In SQL-MAP-Config I set maxActive in 10.

4) The container we are using is jetty. Do you know any problem related with this container? For a while we can´t use JNDI. :(.

When I startup Ibatis (create a instance of DaoMgr), should it open the InitialSize number of connections? Because it´s not creating. Only if I call a query.

tks!





On 8/11/06, Chen, Tim <[EMAIL PROTECTED]> wrote:
1) have you closed your connections in a finally block? opening a new connection for each call is sever.. it *should* be getting some connections from the pool.
2) have you tried playing with maxRequests in <settings>?
3) how many connections before the error msg? (have a dba check for you if you aren't sure) is it possible that you just have the limit set too high?
4) if all else fails use a JNDI connection and setup the connection pool within your container.


From: Renato Silveira [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 11, 2006 9:52 AM

To: [email protected]
Subject: Re: Conections Opened

I still have this problem. Every single call I made a new connection is opened. The DaoManager is started just one time. And the connection remain opened for a  long time until oracle returns a error of max number of connections opened.

Any ideas to solve this problem?

tks!




On 8/11/06, Mkhitaryan, Aram <[EMAIL PROTECTED] > wrote:

When you do first call DBCP creates minimum number of connections

and uses these connections until all connections are busy(active/running) and new connection is created.

 

If you compare first call and second, the first one should take much time then second one.

 

But if "every call I do a new connection is created" that only can mean that your calls are too fast and DBCP

can't create connections automatically and creates during call.

 

Best,

Aram

 


From: Renato Silveira [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 11, 2006 3:45 AM
To: [email protected]
Subject: Re: Conections Opened

 

Hi,

I have configured the maxActive connection with 10 but every call I do a new connection is created.

 <transactionManager type="JDBC">
    <dataSource type="DBCP">
      <property value="${database_driver}" name=" JDBC.Driver"/>
      <property value="${database_url}" name="JDBC.ConnectionURL"/>
      <property value="${database_user}" name="JDBC.Username"/>
      <property value="${database_password}" name=" JDBC.Password"/>
      <property value="10" name="Pool.MaximumActiveConnections"/>
      <property value="5" name="Pool.MaximumIdleConnections"/>
      <property value="6000" name=" Pool.MaximumWait"/>
    </dataSource>
  </transactionManager>

This is my SQL-map-config like. How do I limit the number of opened connections?

tks!

On 8/10/06, Renato Silveira <[EMAIL PROTECTED]> wrote:

Hi,

How many connections are opened by Ibatis to make a simple query?

In my sql-map-config, using SimpleDataSource (pool), the maxnumber of connection are like this:
<property value="1" name=" Pool.MaximumActiveConnections"/>
<property value="1" name="Pool.MaximumIdleConnections"/>
But Ibatis open 4 connections at least.

Cheers!

 



Reply via email to