hi;
The problem is resolved using :
connection-pool maxActive=1000 whenExhaustedAction=2/
so it s strange the message gived by ojb tel us about the broker pool
problem
but the solution was the growing the connection pool !
thx for all.
On 10/27/06, Armin Waibel [EMAIL PROTECTED] wrote:
: Borrow broker from pool failed. in production server
hi;
The problem is resolved using :
connection-pool maxActive=1000 whenExhaustedAction=2/
so it s strange the message gived by ojb tel us about the broker pool
problem
but the solution was the growing the connection pool !
thx for all
3:56 AM
To: OJB Users List
Subject: Re: Borrow broker from pool failed. in production server
hi;
The problem is resolved using :
connection-pool maxActive=1000 whenExhaustedAction=2/
so it s strange the message gived by ojb tel us about the broker pool
problem
but the solution was the growing
the instructions and make the appropriate changes.
-Original Message-
From: Marwane [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 08, 2006 10:28 AM
To: OJB Users List
Subject: Re: Borrow broker from pool failed. in production server
thx for your helpful and constructif reply . i
If you are leaking brokers, that doesn't solve the problem - it just
works around it. We had the same problem with our Spring/JTA/OJB
application and I discovered the problem was due to using Spring DAOs
directly instead of going through the Spring transaction layer.
On 11/8/06, Marwane [EMAIL
thx for your reply.
so we use only the maxActive declared in OJB.properties. in the
repository.xml we dont use
the connection-pool elements.
regards.
On 10/26/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
when i have a quick look it seems to be about the broker pool and not
the connection
Hi,
Marwane wrote:
thx for your reply.
so we use only the maxActive declared in OJB.properties. in the
repository.xml we dont use
the connection-pool elements.
Keep in mind that OJB use two different pools by default. An PB-pool
(settings in OJB.properties file) and a connection-pool
thx.
if i don't defin the connection-pool clause in the repository.xml what is
the default behavor about the
connection managment in ojb ?
On 10/27/06, Armin Waibel [EMAIL PROTECTED] wrote:
Hi,
Marwane wrote:
thx for your reply.
so we use only the maxActive declared in OJB.properties. in
hi
we have a web application on production used about 500 users.
we use default value of ojb parameters (maxActif: 100 ).
we are getting frequently the message indicating that we can't borrow
connection from pool. even if
we use maxActif in 1000 the problem persist.
we need your help and give
when i have a quick look it seems to be about the broker pool and not
the connection pool. Check your OJB.properties and set maxActive to
the same value as maxActive of the connection pool settings in
repository_database.xml. I am not sure about it but your problem
happened to me once this way
]
Sent: Thursday, October 26, 2006 3:11 PM
To: OJB Users List
Subject: Re: Borrow broker from pool failed. in production server
when i have a quick look it seems to be about the broker pool and not
the connection pool. Check your OJB.properties and set maxActive to
the same value as maxActive
11 matches
Mail list logo
