of connection
pooling?) or does it mean that all the traffic is processed over one jdbc
connection?
If latter is the case, I feel like having a connection pool will increase
the performance significantly. Our system might process upto 1000 requests
per second, under forementioned assumptions what would
Hi,
I am not sure about iBatis taking care of connection pooling. But I had
a situation similar to you I have noticed that the creation of the
connection and closing the connection is taken care by iBatis. I have
seen that in the production environment, where we have almost 100
concurrent user
DBCP for pooling?
Thanks in advance.
Erinc
On Thu, Jun 4, 2009 at 1:35 PM, Vinaya Tirikkovalluru
vinaya.tirikkovall...@converge.com wrote:
Hi,
I am not sure about iBatis taking care of connection pooling. But I had a
situation similar to you I have noticed that the creation
as soon as I started the application.
Vinaya
From: Erinc Arikan [mailto:erincari...@gmail.com]
Sent: Thursday, June 04, 2009 3:05 PM
To: user-java@ibatis.apache.org
Subject: Re: JDBC Connection Pooling
Thanks a lot Vinaya;
I already read your
Below is the connection pooling using dbcp BasicDataSource. It all depends on
the value you have given to minIdle propery when you started the application.
As far I know it will never by default create pool size as 10.
bean id=dataSource class=org.apache.commons.dbcp.BasicDataSource
Hi,
I am using Ibatis+Jboss4.2.2
I have not configured connection pooling in Jboss.
Ibatis takes care of everything. But I see a connection in the database
which is open in the morning but still being used, like reused. I just
see a couple of them and not too many.
How could just the 2
Ok, well these would sound funny, but i didn't knew at all before today that
iBatis DAO framework uses connection pooling internally. Anyways i am
somewhat struggling to figure out as to how to disable it..I dont have any
attribute relating to it (and thats why didnt knew at all) but apparently
Thanks for the quick followup Larry
I think i need to give some more details here...
I have already OracleAs (Oc4j) connection pooling setup, and the jndi
datasource (jdbc/proxy) is already configured to use the very connection
pool.
Anyways, last night while trying to test as to what
=xyz/mapping/BeanMapping4.xml/
/sqlMapConfig
mfs wrote:
Ok, well these would sound funny, but i didn't knew at all before today
that iBatis DAO framework uses connection pooling internally. Anyways i am
somewhat struggling to figure out as to how to disable it..I dont have any
attribute
what happens if the ping fails. does the connection getting removed from
the pool?
the reason why i don't have pinging enabled is because i want to control
the case when a connection is closed for one cluster on my own (so i can
switch to another cluster). even if i could solve the problem by
what happens if the ping fails. does the connection getting removed from
the pool?
the reason why i don't have pinging enabled is because i want to control
the case when a connection is closed for one cluster on my own (so i can
switch to another cluster). even if i could solve the problem by
Do you have the ping query (or validation query) enabled?
Cheers,
ClintonOn 11/17/05, mischa [EMAIL PROTECTED] wrote:
is there anything i can do to prevent ibatis from putting backconnetions to the pool when they are already closed? i am working withcluster pairs and when the connection to one
12 matches
Mail list logo