Re: Borrow broker from pool failed. in production server
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 PROTECTED]> wrote: hi; The problem is resolved using : 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: > > Marwane wrote: > > 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 ? > > > > I think by default 30 connections (docs says 21) managed by the pool (if > you specify one of the "pooling" ConnectionFactory implementations in > OJB.properties file). The other properties please see docs > http://db.apache.org/ojb/docu/guides/repository.html#Attributes-N10284 > http://db.apache.org/ojb/docu/guides/connection.html > > regards, > Armin > > > > > > > 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 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 (setting within > >> the connection-pool element in repository file). > >> > >> >> > we use maxActif in 1000 the problem persist. > >> It seems that the error is caused by the broker-pool and not by the > >> connection-pool. Normally the connection is associated with the PB when > >> PB-tx starts or a query is performed - thus always after the PB is > >> requested from the PB-pool. > >> If the suggestions from Eric and Dennis doesn't solve your problem I > >> suppose you have a PB leak in your code. > >> > >> regards, > >> Armin > >> > >> > 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 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 and it was solved by doing as i > suggest. > >> >> > >> >> regards, > >> >> Dennis > >> >> > >> >> 2006/10/26, Marwane <[EMAIL PROTECTED]>: > >> >> > 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 us some leads. > >> >> > > >> >> > stack trace : > >> >> > > >> >> > org.apache.ojb.broker.PBFactoryException: Borrow broker from pool > >> >> failed, > >> >> > using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, > >> >> user=db2bmce, > >> >> > password=* > >> >> > at java.lang.Throwable.(Throwable.java:195) > >> >> > at java.lang.Exception.(Exception.java:41) > >> >> > at java.lang.RuntimeException.(RuntimeException.java:43) > >> >> > at org.apache.commons.lang.exception.NestableRuntimeException > >> >> .( > >> >> > NestableRuntimeException.java:86) > >> >> > at org.apache.ojb.broker.OJBRuntimeException.(Unknown > >> Source) > >> >> > at org.apache.ojb.broker.PBFactoryException.(Unknown > >> Source) > >> >> > at > >> >> > > >> >> > >> > org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.crea
RE: Borrow broker from pool failed. in production server
Well with SQL Server 2005 I use the profiler that comes with the studio, don't know about your database/database tools. You want to have your maxActive settings the same in repository_database.xml and ojb.properties. Then you want to enable eviction threads in your ojb.properties file. Just read 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 will profile the connections, but it will be gretful if you can give me more detail about using DBCP and evictionThreads with example configuration (ojb.prperties, repository.xml) and how to profile the connections with wich tools ? thx On 11/8/06, Ferrer, Eric <[EMAIL PROTECTED]> wrote: > > > Marwane, > > Growing the pool is not a good thing always. Say you have 300 Oracle > licenses, depending on the license, that may include connection pooled > objects under the same user account. > > So there is a section in your code that may not have a finally block so > the connection does not get closed. If your DBA does not have orphan > settings enabled. When you hit your maxActive count and need another > connection, there wont be one available and thus, you will grow you > connection pool maxActive limit. What will happen is you hit your > database max connection limit and will see some nasty error like "ORCL: > 9000 No More Available Connections" < don't quote on that I cant > reproduce a more meanifull error at this point and time. > > So even if you are going to grow make sure you have evictionThreads > running. > > DBCP has an initialSize argument which I believe the OJB Community is > planning to support. Once this is available, using a Database Profiler, > you should be able to start your application up and via the profiler see > new connections per your initialSize. As you need additional resources, > say maxActive is 30, you will see the connection increase to handle the > load. > You should then be able to see eviction thread run to clean up > unused/idle connections. > > I performed a similar test, and found over 45 object calls that did not > have a finally block to close connections and release them back to the > pool. > > Last point, the more connections you have the more memory footprint for > your application will be. Someone else chim in but I believe each > connection takes up to 2MB of memory or that is just what I can see from > the Database Profiler. > > -Eric > > -Original Message- > From: Marwane [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 08, 2006 3:56 AM > To: OJB Users List > Subject: Re: Borrow broker from pool failed. in production server > > hi; > The problem is resolved using : > > > 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: > > > > Marwane wrote: > > > 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 ? > > > > > > > I think by default 30 connections (docs says 21) managed by the pool > (if > > you specify one of the "pooling" ConnectionFactory implementations in > > OJB.properties file). The other properties please see docs > > http://db.apache.org/ojb/docu/guides/repository.html#Attributes-N10284 > > http://db.apache.org/ojb/docu/guides/connection.html > > > > regards, > > Armin > > > > > > > > > > > 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 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 (setting > within > > >> the connection-pool element in repository file). > > >> > > >> >> > we use maxActif in 1000 the problem persist. > > >> It seems that the error is caused by the broker-pool and not by the > > >> connection-pool. No
Re: Borrow broker from pool failed. in production server
thx for your helpful and constructif reply . i will profile the connections, but it will be gretful if you can give me more detail about using DBCP and evictionThreads with example configuration (ojb.prperties, repository.xml) and how to profile the connections with wich tools ? thx On 11/8/06, Ferrer, Eric <[EMAIL PROTECTED]> wrote: Marwane, Growing the pool is not a good thing always. Say you have 300 Oracle licenses, depending on the license, that may include connection pooled objects under the same user account. So there is a section in your code that may not have a finally block so the connection does not get closed. If your DBA does not have orphan settings enabled. When you hit your maxActive count and need another connection, there wont be one available and thus, you will grow you connection pool maxActive limit. What will happen is you hit your database max connection limit and will see some nasty error like "ORCL: 9000 No More Available Connections" < don't quote on that I cant reproduce a more meanifull error at this point and time. So even if you are going to grow make sure you have evictionThreads running. DBCP has an initialSize argument which I believe the OJB Community is planning to support. Once this is available, using a Database Profiler, you should be able to start your application up and via the profiler see new connections per your initialSize. As you need additional resources, say maxActive is 30, you will see the connection increase to handle the load. You should then be able to see eviction thread run to clean up unused/idle connections. I performed a similar test, and found over 45 object calls that did not have a finally block to close connections and release them back to the pool. Last point, the more connections you have the more memory footprint for your application will be. Someone else chim in but I believe each connection takes up to 2MB of memory or that is just what I can see from the Database Profiler. -Eric -Original Message- From: Marwane [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 08, 2006 3:56 AM To: OJB Users List Subject: Re: Borrow broker from pool failed. in production server hi; The problem is resolved using : 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: > > Marwane wrote: > > 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 ? > > > > I think by default 30 connections (docs says 21) managed by the pool (if > you specify one of the "pooling" ConnectionFactory implementations in > OJB.properties file). The other properties please see docs > http://db.apache.org/ojb/docu/guides/repository.html#Attributes-N10284 > http://db.apache.org/ojb/docu/guides/connection.html > > regards, > Armin > > > > > > > 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 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 (setting within > >> the connection-pool element in repository file). > >> > >> >> > we use maxActif in 1000 the problem persist. > >> It seems that the error is caused by the broker-pool and not by the > >> connection-pool. Normally the connection is associated with the PB when > >> PB-tx starts or a query is performed - thus always after the PB is > >> requested from the PB-pool. > >> If the suggestions from Eric and Dennis doesn't solve your problem I > >> suppose you have a PB leak in your code. > >> > >> regards, > >> Armin > >> > >> > 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 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 and it was solved by doing
RE: Borrow broker from pool failed. in production server
Marwane, Growing the pool is not a good thing always. Say you have 300 Oracle licenses, depending on the license, that may include connection pooled objects under the same user account. So there is a section in your code that may not have a finally block so the connection does not get closed. If your DBA does not have orphan settings enabled. When you hit your maxActive count and need another connection, there wont be one available and thus, you will grow you connection pool maxActive limit. What will happen is you hit your database max connection limit and will see some nasty error like "ORCL: 9000 No More Available Connections" < don't quote on that I cant reproduce a more meanifull error at this point and time. So even if you are going to grow make sure you have evictionThreads running. DBCP has an initialSize argument which I believe the OJB Community is planning to support. Once this is available, using a Database Profiler, you should be able to start your application up and via the profiler see new connections per your initialSize. As you need additional resources, say maxActive is 30, you will see the connection increase to handle the load. You should then be able to see eviction thread run to clean up unused/idle connections. I performed a similar test, and found over 45 object calls that did not have a finally block to close connections and release them back to the pool. Last point, the more connections you have the more memory footprint for your application will be. Someone else chim in but I believe each connection takes up to 2MB of memory or that is just what I can see from the Database Profiler. -Eric -Original Message- From: Marwane [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 08, 2006 3:56 AM To: OJB Users List Subject: Re: Borrow broker from pool failed. in production server hi; The problem is resolved using : 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: > > Marwane wrote: > > 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 ? > > > > I think by default 30 connections (docs says 21) managed by the pool (if > you specify one of the "pooling" ConnectionFactory implementations in > OJB.properties file). The other properties please see docs > http://db.apache.org/ojb/docu/guides/repository.html#Attributes-N10284 > http://db.apache.org/ojb/docu/guides/connection.html > > regards, > Armin > > > > > > > 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 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 (setting within > >> the connection-pool element in repository file). > >> > >> >> > we use maxActif in 1000 the problem persist. > >> It seems that the error is caused by the broker-pool and not by the > >> connection-pool. Normally the connection is associated with the PB when > >> PB-tx starts or a query is performed - thus always after the PB is > >> requested from the PB-pool. > >> If the suggestions from Eric and Dennis doesn't solve your problem I > >> suppose you have a PB leak in your code. > >> > >> regards, > >> Armin > >> > >> > 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 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 and it was solved by doing as i > suggest. > >> >> > >> >> regards, > >> >> Dennis > >> >> > >> >> 2006/10/26, Marwane <[EMAIL PROTECTED]>: > >> >> > hi > >> >> > we have a web application on production used about 500 users. > >> >> > we use default value of ojb parameters (maxActif: 100 ).
Re: Borrow broker from pool failed. in production server
hi; The problem is resolved using : 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: Marwane wrote: > 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 ? > I think by default 30 connections (docs says 21) managed by the pool (if you specify one of the "pooling" ConnectionFactory implementations in OJB.properties file). The other properties please see docs http://db.apache.org/ojb/docu/guides/repository.html#Attributes-N10284 http://db.apache.org/ojb/docu/guides/connection.html regards, Armin > > > 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 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 (setting within >> the connection-pool element in repository file). >> >> >> > we use maxActif in 1000 the problem persist. >> It seems that the error is caused by the broker-pool and not by the >> connection-pool. Normally the connection is associated with the PB when >> PB-tx starts or a query is performed - thus always after the PB is >> requested from the PB-pool. >> If the suggestions from Eric and Dennis doesn't solve your problem I >> suppose you have a PB leak in your code. >> >> regards, >> Armin >> >> > 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 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 and it was solved by doing as i suggest. >> >> >> >> regards, >> >> Dennis >> >> >> >> 2006/10/26, Marwane <[EMAIL PROTECTED]>: >> >> > 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 us some leads. >> >> > >> >> > stack trace : >> >> > >> >> > org.apache.ojb.broker.PBFactoryException: Borrow broker from pool >> >> failed, >> >> > using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, >> >> user=db2bmce, >> >> > password=* >> >> > at java.lang.Throwable.(Throwable.java:195) >> >> > at java.lang.Exception.(Exception.java:41) >> >> > at java.lang.RuntimeException.(RuntimeException.java:43) >> >> > at org.apache.commons.lang.exception.NestableRuntimeException >> >> .( >> >> > NestableRuntimeException.java:86) >> >> > at org.apache.ojb.broker.OJBRuntimeException.(Unknown >> Source) >> >> > at org.apache.ojb.broker.PBFactoryException.(Unknown >> Source) >> >> > at >> >> > >> >> >> org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersistenceBroker >> >> >> >> >> (Unknown >> >> > Source) >> >> > at >> >> > >> >> >> org.apache.ojb.broker.core.PersistenceBrokerFactoryBaseImpl.defaultPersistenceBroker >> >> >> >> >> (Unknown >> >> > Source) >> >> > at >> >> > >> org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker >> >> (Unknown >> >> > Source) >> >> > at >> >> > >> >> >> ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.getBroker( >> >> >> >> >> > OJBPersistenceService.java:156) >> >> >
Re: Borrow broker from pool failed. in production server
Marwane wrote: 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 ? I think by default 30 connections (docs says 21) managed by the pool (if you specify one of the "pooling" ConnectionFactory implementations in OJB.properties file). The other properties please see docs http://db.apache.org/ojb/docu/guides/repository.html#Attributes-N10284 http://db.apache.org/ojb/docu/guides/connection.html regards, Armin 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 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 (setting within the connection-pool element in repository file). >> > we use maxActif in 1000 the problem persist. It seems that the error is caused by the broker-pool and not by the connection-pool. Normally the connection is associated with the PB when PB-tx starts or a query is performed - thus always after the PB is requested from the PB-pool. If the suggestions from Eric and Dennis doesn't solve your problem I suppose you have a PB leak in your code. regards, Armin > 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 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 and it was solved by doing as i suggest. >> >> regards, >> Dennis >> >> 2006/10/26, Marwane <[EMAIL PROTECTED]>: >> > 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 us some leads. >> > >> > stack trace : >> > >> > org.apache.ojb.broker.PBFactoryException: Borrow broker from pool >> failed, >> > using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, >> user=db2bmce, >> > password=* >> > at java.lang.Throwable.(Throwable.java:195) >> > at java.lang.Exception.(Exception.java:41) >> > at java.lang.RuntimeException.(RuntimeException.java:43) >> > at org.apache.commons.lang.exception.NestableRuntimeException >> .( >> > NestableRuntimeException.java:86) >> > at org.apache.ojb.broker.OJBRuntimeException.(Unknown Source) >> > at org.apache.ojb.broker.PBFactoryException.(Unknown Source) >> > at >> > >> org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersistenceBroker >> >> (Unknown >> > Source) >> > at >> > >> org.apache.ojb.broker.core.PersistenceBrokerFactoryBaseImpl.defaultPersistenceBroker >> >> (Unknown >> > Source) >> > at >> > org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker >> (Unknown >> > Source) >> > at >> > >> ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.getBroker( >> >> > OJBPersistenceService.java:156) >> > at >> > >> ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.newSession >> >> ( >> > OJBPersistenceService.java:250) >> > at >> > >> ma.co.omnidata.framework.services.transaction.impl.TransactionManagerImpl.getTransaction >> >> > (TransactionManagerImpl.java:39) >> > at >> > >> ma.co.omnidata.framework.services.businessInterface.OMNIFacade.invokeService >> >> > (OMNIFacade.java:55) >> > at >> > >> ma.co.omnidata.framework.services.ihm.struts.core.OMNIBaseAction.invokeBusiness >> >> > (OMNIBaseAction.java:120) >> > at >> > >> com.rmawatanya.convergence.application.technique.habilitation.ihm.action.HabLogonAction.doExecute >> >> > (HabLogonAction.java:47) >> > at >> > >> com.rmawatanya.convergence.application.technique.habilitation.ihm.action.HabLogonAction.execute >> >> > (HabLogonAction.java:35) >
Re: Borrow broker from pool failed. in production server
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 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 (setting within the connection-pool element in repository file). >> > we use maxActif in 1000 the problem persist. It seems that the error is caused by the broker-pool and not by the connection-pool. Normally the connection is associated with the PB when PB-tx starts or a query is performed - thus always after the PB is requested from the PB-pool. If the suggestions from Eric and Dennis doesn't solve your problem I suppose you have a PB leak in your code. regards, Armin > 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 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 and it was solved by doing as i suggest. >> >> regards, >> Dennis >> >> 2006/10/26, Marwane <[EMAIL PROTECTED]>: >> > 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 us some leads. >> > >> > stack trace : >> > >> > org.apache.ojb.broker.PBFactoryException: Borrow broker from pool >> failed, >> > using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, >> user=db2bmce, >> > password=* >> > at java.lang.Throwable.(Throwable.java:195) >> > at java.lang.Exception.(Exception.java:41) >> > at java.lang.RuntimeException.(RuntimeException.java:43) >> > at org.apache.commons.lang.exception.NestableRuntimeException >> .( >> > NestableRuntimeException.java:86) >> > at org.apache.ojb.broker.OJBRuntimeException.(Unknown Source) >> > at org.apache.ojb.broker.PBFactoryException.(Unknown Source) >> > at >> > >> org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersistenceBroker >> >> (Unknown >> > Source) >> > at >> > >> org.apache.ojb.broker.core.PersistenceBrokerFactoryBaseImpl.defaultPersistenceBroker >> >> (Unknown >> > Source) >> > at >> > org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker >> (Unknown >> > Source) >> > at >> > >> ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.getBroker( >> >> > OJBPersistenceService.java:156) >> > at >> > >> ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.newSession >> >> ( >> > OJBPersistenceService.java:250) >> > at >> > >> ma.co.omnidata.framework.services.transaction.impl.TransactionManagerImpl.getTransaction >> >> > (TransactionManagerImpl.java:39) >> > at >> > >> ma.co.omnidata.framework.services.businessInterface.OMNIFacade.invokeService >> >> > (OMNIFacade.java:55) >> > at >> > >> ma.co.omnidata.framework.services.ihm.struts.core.OMNIBaseAction.invokeBusiness >> >> > (OMNIBaseAction.java:120) >> > at >> > >> com.rmawatanya.convergence.application.technique.habilitation.ihm.action.HabLogonAction.doExecute >> >> > (HabLogonAction.java:47) >> > at >> > >> com.rmawatanya.convergence.application.technique.habilitation.ihm.action.HabLogonAction.execute >> >> > (HabLogonAction.java:35) >> > at org.apache.struts.action.RequestProcessor.processActionPerform ( >> > RequestProcessor.java:421) >> > at org.apache.struts.action.RequestProcessor.process( >> > RequestProcessor.java:226) >> > at >> org.apache.struts.action.ActionServlet.process(ActionServlet.java >> > :1164) >> > at org.apache.struts.action.ActionServlet.doPost( ActionServlet
Re: Borrow broker from pool failed. in production server
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 (setting within the connection-pool element in repository file). >> > we use maxActif in 1000 the problem persist. It seems that the error is caused by the broker-pool and not by the connection-pool. Normally the connection is associated with the PB when PB-tx starts or a query is performed - thus always after the PB is requested from the PB-pool. If the suggestions from Eric and Dennis doesn't solve your problem I suppose you have a PB leak in your code. regards, Armin 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 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 and it was solved by doing as i suggest. regards, Dennis 2006/10/26, Marwane <[EMAIL PROTECTED]>: > 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 us some leads. > > stack trace : > > org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed, > using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, user=db2bmce, > password=* > at java.lang.Throwable.(Throwable.java:195) > at java.lang.Exception.(Exception.java:41) > at java.lang.RuntimeException.(RuntimeException.java:43) > at org.apache.commons.lang.exception.NestableRuntimeException .( > NestableRuntimeException.java:86) > at org.apache.ojb.broker.OJBRuntimeException.(Unknown Source) > at org.apache.ojb.broker.PBFactoryException.(Unknown Source) > at > org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersistenceBroker (Unknown > Source) > at > org.apache.ojb.broker.core.PersistenceBrokerFactoryBaseImpl.defaultPersistenceBroker (Unknown > Source) > at > org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker (Unknown > Source) > at > ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.getBroker( > OJBPersistenceService.java:156) > at > ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.newSession ( > OJBPersistenceService.java:250) > at > ma.co.omnidata.framework.services.transaction.impl.TransactionManagerImpl.getTransaction > (TransactionManagerImpl.java:39) > at > ma.co.omnidata.framework.services.businessInterface.OMNIFacade.invokeService > (OMNIFacade.java:55) > at > ma.co.omnidata.framework.services.ihm.struts.core.OMNIBaseAction.invokeBusiness > (OMNIBaseAction.java:120) > at > com.rmawatanya.convergence.application.technique.habilitation.ihm.action.HabLogonAction.doExecute > (HabLogonAction.java:47) > at > com.rmawatanya.convergence.application.technique.habilitation.ihm.action.HabLogonAction.execute > (HabLogonAction.java:35) > at org.apache.struts.action.RequestProcessor.processActionPerform( > RequestProcessor.java:421) > at org.apache.struts.action.RequestProcessor.process( > RequestProcessor.java:226) > at org.apache.struts.action.ActionServlet.process(ActionServlet.java > :1164) > at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java :415) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:851) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.service( > ServletWrapper.java:1246) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest( > ServletWrapper.java:380) > at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest ( > CacheServletWrapper.java:80) > at com.ibm.ws.webcontainer.WebContainer.handleRequest( WebContainer.java > :1724) > at com.ibm.ws.webcontainer.channel.WCChannelLink.ready( > WCChannelLink.java:79) > at > com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination( > HttpInboundLink.java:422) > at > com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation( > HttpInboundLink.java:319) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready( > HttpInboundLink.java:288) > at &
Re: Borrow broker from pool failed. in production server
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 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 and it was solved by doing as i suggest. regards, Dennis 2006/10/26, Marwane <[EMAIL PROTECTED]>: > 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 us some leads. > > stack trace : > > org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed, > using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, user=db2bmce, > password=* > at java.lang.Throwable.(Throwable.java:195) > at java.lang.Exception.(Exception.java:41) > at java.lang.RuntimeException.(RuntimeException.java:43) > at org.apache.commons.lang.exception.NestableRuntimeException .( > NestableRuntimeException.java:86) > at org.apache.ojb.broker.OJBRuntimeException.(Unknown Source) > at org.apache.ojb.broker.PBFactoryException.(Unknown Source) > at > org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersistenceBroker (Unknown > Source) > at > org.apache.ojb.broker.core.PersistenceBrokerFactoryBaseImpl.defaultPersistenceBroker (Unknown > Source) > at > org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker (Unknown > Source) > at > ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.getBroker( > OJBPersistenceService.java:156) > at > ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.newSession ( > OJBPersistenceService.java:250) > at > ma.co.omnidata.framework.services.transaction.impl.TransactionManagerImpl.getTransaction > (TransactionManagerImpl.java:39) > at > ma.co.omnidata.framework.services.businessInterface.OMNIFacade.invokeService > (OMNIFacade.java:55) > at > ma.co.omnidata.framework.services.ihm.struts.core.OMNIBaseAction.invokeBusiness > (OMNIBaseAction.java:120) > at > com.rmawatanya.convergence.application.technique.habilitation.ihm.action.HabLogonAction.doExecute > (HabLogonAction.java:47) > at > com.rmawatanya.convergence.application.technique.habilitation.ihm.action.HabLogonAction.execute > (HabLogonAction.java:35) > at org.apache.struts.action.RequestProcessor.processActionPerform( > RequestProcessor.java:421) > at org.apache.struts.action.RequestProcessor.process( > RequestProcessor.java:226) > at org.apache.struts.action.ActionServlet.process(ActionServlet.java > :1164) > at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java :415) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:851) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.service( > ServletWrapper.java:1246) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest( > ServletWrapper.java:380) > at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest ( > CacheServletWrapper.java:80) > at com.ibm.ws.webcontainer.WebContainer.handleRequest( WebContainer.java > :1724) > at com.ibm.ws.webcontainer.channel.WCChannelLink.ready( > WCChannelLink.java:79) > at > com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination( > HttpInboundLink.java:422) > at > com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation( > HttpInboundLink.java:319) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready( > HttpInboundLink.java:288) > at > com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters > (NewConnectionInitialReadCallback.java:207) > at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete > (NewConnectionInitialReadCallback.java:109) > at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete( > WorkQueueManager.java:537) > at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO( > WorkQueueManager.java:593) > at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun( > WorkQueueManager.java:946) > at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run( > WorkQueueManager.java:1038) > at com.ibm.ws.util.Thr
RE: Borrow broker from pool failed. in production server
One thing to consider. Take a look at the database and find out how many licenses you have. When I was an OJB/DBCP noob I had set the maxActive higher than the number of available connections in the database. - Eric -Original Message- From: Dennis Bekkering [mailto:[EMAIL PROTECTED] 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 of the connection pool settings in repository_database.xml. I am not sure about it but your problem happened to me once this way and it was solved by doing as i suggest. regards, Dennis 2006/10/26, Marwane <[EMAIL PROTECTED]>: > 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 us some leads. > > stack trace : > > org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed, > using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, user=db2bmce, > password=* > at java.lang.Throwable.(Throwable.java:195) > at java.lang.Exception.(Exception.java:41) > at java.lang.RuntimeException.(RuntimeException.java:43) > at org.apache.commons.lang.exception.NestableRuntimeException.( > NestableRuntimeException.java:86) > at org.apache.ojb.broker.OJBRuntimeException.(Unknown Source) > at org.apache.ojb.broker.PBFactoryException.(Unknown Source) > at > org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPer sistenceBroker(Unknown > Source) > at > org.apache.ojb.broker.core.PersistenceBrokerFactoryBaseImpl.defaultPersi stenceBroker(Unknown > Source) > at > org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker( Unknown > Source) > at > ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.getBroke r( > OJBPersistenceService.java:156) > at > ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.newSessi on( > OJBPersistenceService.java:250) > at > ma.co.omnidata.framework.services.transaction.impl.TransactionManagerImp l.getTransaction > (TransactionManagerImpl.java:39) > at > ma.co.omnidata.framework.services.businessInterface.OMNIFacade.invokeSer vice > (OMNIFacade.java:55) > at > ma.co.omnidata.framework.services.ihm.struts.core.OMNIBaseAction.invokeB usiness > (OMNIBaseAction.java:120) > at > com.rmawatanya.convergence.application.technique.habilitation.ihm.action .HabLogonAction.doExecute > (HabLogonAction.java:47) > at > com.rmawatanya.convergence.application.technique.habilitation.ihm.action .HabLogonAction.execute > (HabLogonAction.java:35) > at org.apache.struts.action.RequestProcessor.processActionPerform( > RequestProcessor.java:421) > at org.apache.struts.action.RequestProcessor.process( > RequestProcessor.java:226) > at org.apache.struts.action.ActionServlet.process(ActionServlet.java > :1164) > at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:851) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.service( > ServletWrapper.java:1246) > at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest( > ServletWrapper.java:380) > at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest( > CacheServletWrapper.java:80) > at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java > :1724) > at com.ibm.ws.webcontainer.channel.WCChannelLink.ready( > WCChannelLink.java:79) > at > com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscriminatio n( > HttpInboundLink.java:422) > at > com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformatio n( > HttpInboundLink.java:319) > at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready( > HttpInboundLink.java:288) > at > com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscr iminaters > (NewConnectionInitialReadCallback.java:207) > at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete > (NewConnectionInitialReadCallback.java:109) > at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete( > WorkQueueManager.java:537) > at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO( > WorkQueueManager.java:593) &
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 of the connection pool settings in repository_database.xml. I am not sure about it but your problem happened to me once this way and it was solved by doing as i suggest. regards, Dennis 2006/10/26, Marwane <[EMAIL PROTECTED]>: 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 us some leads. stack trace : org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed, using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, user=db2bmce, password=* at java.lang.Throwable.(Throwable.java:195) at java.lang.Exception.(Exception.java:41) at java.lang.RuntimeException.(RuntimeException.java:43) at org.apache.commons.lang.exception.NestableRuntimeException.( NestableRuntimeException.java:86) at org.apache.ojb.broker.OJBRuntimeException.(Unknown Source) at org.apache.ojb.broker.PBFactoryException.(Unknown Source) at org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersistenceBroker(Unknown Source) at org.apache.ojb.broker.core.PersistenceBrokerFactoryBaseImpl.defaultPersistenceBroker(Unknown Source) at org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker(Unknown Source) at ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.getBroker( OJBPersistenceService.java:156) at ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.newSession( OJBPersistenceService.java:250) at ma.co.omnidata.framework.services.transaction.impl.TransactionManagerImpl.getTransaction (TransactionManagerImpl.java:39) at ma.co.omnidata.framework.services.businessInterface.OMNIFacade.invokeService (OMNIFacade.java:55) at ma.co.omnidata.framework.services.ihm.struts.core.OMNIBaseAction.invokeBusiness (OMNIBaseAction.java:120) at com.rmawatanya.convergence.application.technique.habilitation.ihm.action.HabLogonAction.doExecute (HabLogonAction.java:47) at com.rmawatanya.convergence.application.technique.habilitation.ihm.action.HabLogonAction.execute (HabLogonAction.java:35) at org.apache.struts.action.RequestProcessor.processActionPerform( RequestProcessor.java:421) at org.apache.struts.action.RequestProcessor.process( RequestProcessor.java:226) at org.apache.struts.action.ActionServlet.process(ActionServlet.java :1164) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415) at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) at javax.servlet.http.HttpServlet.service(HttpServlet.java:851) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service( ServletWrapper.java:1246) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest( ServletWrapper.java:380) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest( CacheServletWrapper.java:80) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java :1724) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready( WCChannelLink.java:79) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination( HttpInboundLink.java:422) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation( HttpInboundLink.java:319) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready( HttpInboundLink.java:288) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters (NewConnectionInitialReadCallback.java:207) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete (NewConnectionInitialReadCallback.java:109) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete( WorkQueueManager.java:537) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO( WorkQueueManager.java:593) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun( WorkQueueManager.java:946) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run( WorkQueueManager.java:1038) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1446) Caused by: java.util.NoSuchElementException at java.lang.Throwable.(Throwable.java:180) at java.lang.Exception.(Exception.java:29) at java.lang.RuntimeException.(RuntimeException.java:32) at java.util.NoSuchElementException.(NoSuchElementException.java :28) at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject( GenericKeyedObjectPool.java:760) ... 31 more [18/10/06 11:59:53:253 TUC] 0379 SystemErr R org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed, using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, user=db2bmce, password=* at java.lan
Borrow broker from pool failed. in production server
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 us some leads. stack trace : org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed, using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, user=db2bmce, password=* at java.lang.Throwable.(Throwable.java:195) at java.lang.Exception.(Exception.java:41) at java.lang.RuntimeException.(RuntimeException.java:43) at org.apache.commons.lang.exception.NestableRuntimeException.( NestableRuntimeException.java:86) at org.apache.ojb.broker.OJBRuntimeException.(Unknown Source) at org.apache.ojb.broker.PBFactoryException.(Unknown Source) at org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersistenceBroker(Unknown Source) at org.apache.ojb.broker.core.PersistenceBrokerFactoryBaseImpl.defaultPersistenceBroker(Unknown Source) at org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker(Unknown Source) at ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.getBroker( OJBPersistenceService.java:156) at ma.co.omnidata.framework.services.dao.ojb.OJBPersistenceService.newSession( OJBPersistenceService.java:250) at ma.co.omnidata.framework.services.transaction.impl.TransactionManagerImpl.getTransaction (TransactionManagerImpl.java:39) at ma.co.omnidata.framework.services.businessInterface.OMNIFacade.invokeService (OMNIFacade.java:55) at ma.co.omnidata.framework.services.ihm.struts.core.OMNIBaseAction.invokeBusiness (OMNIBaseAction.java:120) at com.rmawatanya.convergence.application.technique.habilitation.ihm.action.HabLogonAction.doExecute (HabLogonAction.java:47) at com.rmawatanya.convergence.application.technique.habilitation.ihm.action.HabLogonAction.execute (HabLogonAction.java:35) at org.apache.struts.action.RequestProcessor.processActionPerform( RequestProcessor.java:421) at org.apache.struts.action.RequestProcessor.process( RequestProcessor.java:226) at org.apache.struts.action.ActionServlet.process(ActionServlet.java :1164) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:415) at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) at javax.servlet.http.HttpServlet.service(HttpServlet.java:851) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service( ServletWrapper.java:1246) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest( ServletWrapper.java:380) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest( CacheServletWrapper.java:80) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java :1724) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready( WCChannelLink.java:79) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination( HttpInboundLink.java:422) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation( HttpInboundLink.java:319) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready( HttpInboundLink.java:288) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminaters (NewConnectionInitialReadCallback.java:207) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete (NewConnectionInitialReadCallback.java:109) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.requestComplete( WorkQueueManager.java:537) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attemptIO( WorkQueueManager.java:593) at com.ibm.ws.tcp.channel.impl.WorkQueueManager.workerRun( WorkQueueManager.java:946) at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worker.run( WorkQueueManager.java:1038) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1446) Caused by: java.util.NoSuchElementException at java.lang.Throwable.(Throwable.java:180) at java.lang.Exception.(Exception.java:29) at java.lang.RuntimeException.(RuntimeException.java:32) at java.util.NoSuchElementException.(NoSuchElementException.java :28) at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject( GenericKeyedObjectPool.java:760) ... 31 more [18/10/06 11:59:53:253 TUC] 0379 SystemErr R org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed, using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, user=db2bmce, password=* at java.lang.Throwable.(Throwable.java:195) at java.lang.Exception.(Exception.java:41) at java.lang.RuntimeException.(RuntimeException.java:43) at org.apache.commons.lang.exception.NestableRuntimeException.( NestableRuntimeException.java:86) at org.apache.ojb.broker.OJBRuntimeException.(Unknown Source) at org.apache.ojb.broker.PBFactoryException.(Unknown Source) at org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersistenceB
Re: Borrow broker from pool failed
Yes i got this message error one day and it was because i don t close the broker. good luck On 3/8/06, Rick Roman <[EMAIL PROTECTED]> wrote: > > I have been getting this error message intermittently. Would this > message result from running out of connections, like I failed to close > the broker in some function? > > Servlet.service() for servlet action threw exception > failed, using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, > user=null, password=null>org.apache.ojb.broker.PBFactoryException: > Borrow broker from pool failed, using PBKey org.apache.ojb.broker.PBKey: > jcdAlias=default, user=null, password=null > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Borrow broker from pool failed
I have been getting this error message intermittently. Would this message result from running out of connections, like I failed to close the broker in some function? Servlet.service() for servlet action threw exception org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed, using PBKey org.apache.ojb.broker.PBKey: jcdAlias=default, user=null, password=null - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Borrow broker from pool failed
Peter Juszack wrote: Hallo Thomas, vielen Dank für Deine Hinweise. Wir versuchen hier gerade auf OJB 1.0.1 zu updaten. Dem ojb JAR aus dem Binarypaket fehlen allerding die org.apapche.ojb.jboss.* - Klassen, die für den JNDI-Kram erforderlich sind. richtig, die Klassen wurden entfernt, da sie eigentlich nichts mit OJB zu tun haben und es für uns nicht möglich ist für jeden appServer eine solche service Klasse vorzuhalten. Sollte allerdings kein Problem sein die "alten" JBoss Klassen in OJB 1.0.1 zu integrieren. Ist Selbstkompillieren des OJB die einzige Möglichkeit oder bekommt man noch irgendwo ein fertiges JAR, in dem alle Klassen enthalten sind? Die Klassen taten nichts anderes als die PBF (oder odmg interfaces) über JNDI zur Verfügung zu stellen. Dazu muß OJB nicht selbst kompiliert werden, es reicht eine solche service Klasse zu schreiben. Gruß Armin Gruß Peter - Original Message - From: "Thomas Franke" <[EMAIL PROTECTED]> To: "OJB Users List" Sent: Wednesday, February 16, 2005 12:21 PM Subject: Re: Borrow broker from pool failed Peter Juszack wrote: we use OJB 1.0-rc5 together with JBoss 3.2.1 and EJB in a production environment. The system is up for about one and a half years. The problem is, that we have to restart the JBoss application server once a week. This is necessary because new ServerContexts (Logins) can't get a persistence broker from the pool (stack tarce follows). I know that problem. We had the same a time ago. I think there are 2 solutions: First you must close each broker with broker.close. Check your code for this. Second it seems this is a bug in your ojb version. Since we changed to ojb 1.0.1 we haven't had this problem anymore. The change from 1.0-rc5 to 1.0.1 was really easy and without any trouble. good luck regards Thomas -- Mit freundlichen Grüßen Thomas Franke Geschäftsführer Leiter Entwicklung the energy for a better world softEnergy GmbH Platz der Freundschaft 1 18059 Rostock fon: +49 381 40 587 535 fax: +49 381 40 587 555 mobil: +49 1715222015 http://www.softenergy.de mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Borrow broker from pool failed
Hallo Peter, vielen Dank für Deine Hinweise. Wir versuchen hier gerade auf OJB 1.0.1 zu updaten. Dem ojb JAR aus dem Binarypaket fehlen allerding die org.apapche.ojb.jboss.* - Klassen, die für den JNDI-Kram erforderlich sind. Ist Selbstkompillieren des OJB die einzige Möglichkeit oder bekommt man noch irgendwo ein fertiges JAR, in dem alle Klassen enthalten sind? Dazu kann ich gar nichts sagen, weil das bisher in unserem Projekt nicht anwenden. Tut mir leid. Kann man nicht die fehlenden Klassen auch als extra jar mitgeben? -- Mit freundlichen Grüßen Thomas Franke Geschäftsführer Leiter Entwicklung the energy for a better world softEnergy GmbH Platz der Freundschaft 1 18059 Rostock fon: +49 381 40 587 535 fax: +49 381 40 587 555 mobil: +49 1715222015 http://www.softenergy.de mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Borrow broker from pool failed
Hallo Thomas, vielen Dank für Deine Hinweise. Wir versuchen hier gerade auf OJB 1.0.1 zu updaten. Dem ojb JAR aus dem Binarypaket fehlen allerding die org.apapche.ojb.jboss.* - Klassen, die für den JNDI-Kram erforderlich sind. Ist Selbstkompillieren des OJB die einzige Möglichkeit oder bekommt man noch irgendwo ein fertiges JAR, in dem alle Klassen enthalten sind? Gruß Peter - Original Message - From: "Thomas Franke" <[EMAIL PROTECTED]> To: "OJB Users List" Sent: Wednesday, February 16, 2005 12:21 PM Subject: Re: Borrow broker from pool failed > Peter Juszack wrote: > > > we use OJB 1.0-rc5 together with JBoss 3.2.1 and EJB in a production > > environment. The system is up for about one and a half years. The > > problem is, that we have to restart the JBoss application server once > > a week. This is necessary because new ServerContexts (Logins) can't > > get a persistence broker from the pool (stack tarce follows). > I know that problem. We had the same a time ago. I think there are 2 > solutions: First you must close each broker with broker.close. Check > your code for this. Second it seems this is a bug in your ojb version. > Since we changed to ojb 1.0.1 we haven't had this problem anymore. > The change from 1.0-rc5 to 1.0.1 was really easy and without any trouble. > > good luck > > regards > > Thomas > > -- > Mit freundlichen Grüßen > > Thomas Franke > > Geschäftsführer > Leiter Entwicklung > > the energy for a better world > > softEnergy GmbH > Platz der Freundschaft 1 > 18059 Rostock > > fon: +49 381 40 587 535 > fax: +49 381 40 587 555 > mobil: +49 1715222015 > > http://www.softenergy.de > mail: [EMAIL PROTECTED] > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Borrow broker from pool failed
Peter Juszack wrote: we use OJB 1.0-rc5 together with JBoss 3.2.1 and EJB in a production environment. The system is up for about one and a half years. The problem is, that we have to restart the JBoss application server once a week. This is necessary because new ServerContexts (Logins) can't get a persistence broker from the pool (stack tarce follows). I know that problem. We had the same a time ago. I think there are 2 solutions: First you must close each broker with broker.close. Check your code for this. Second it seems this is a bug in your ojb version. Since we changed to ojb 1.0.1 we haven't had this problem anymore. The change from 1.0-rc5 to 1.0.1 was really easy and without any trouble. good luck regards Thomas -- Mit freundlichen Grüßen Thomas Franke Geschäftsführer Leiter Entwicklung the energy for a better world softEnergy GmbH Platz der Freundschaft 1 18059 Rostock fon: +49 381 40 587 535 fax: +49 381 40 587 555 mobil: +49 1715222015 http://www.softenergy.de mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Borrow broker from pool failed
at de.hkw.lekos.server.core.AbstractMaintenanceBean.log(AbstractMaintenanceBean.java:97) at de.hkw.lekos.server.ejb.sb.benutzer.BenutzerMaintenanceBean.login(BenutzerMaintenanceBean.java:114) at sun.reflect.GeneratedMethodAccessor560.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java: 629) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor .java:186) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceIntercepto r.java:72) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:84) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:243) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:104) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:117) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionContainer.java:322) at org.jboss.ejb.Container.invoke(Container.java:674) at sun.reflect.GeneratedMethodAccessor36.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:359) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:534) rethrown as org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed, using PBKey org.apache.ojb.broker.PB Key: jcdAlias=default, user=lekos, password=* at org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersistenceBroker(PersistenceB rokerFactoryDefaultImpl.java:156) at org.apache.ojb.broker.core.PersistenceBrokerFactoryBaseImpl.defaultPersistenceBroker(PersistenceBro kerFactoryBaseImpl.java:197) at de.hkw.lekos.server.core.AbstractSessionBean.getBroker(AbstractSessionBean.java:104) at de.hkw.lekos.server.core.AbstractMaintenanceBean.storeObject(AbstractMaintenanceBean.java:292) at de.hkw.lekos.server.core.AbstractMaintenanceBean.log(AbstractMaintenanceBean.java:97) at de.hkw.lekos.server.ejb.sb.benutzer.BenutzerMaintenanceBean.login(BenutzerMaintenanceBean.java:114) at sun.reflect.GeneratedMethodAccessor560.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java: 629) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor .java:186) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceIntercepto r.java:72) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:84) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:243) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:104) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:117) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:191) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.StatelessSessionContainer.internalInvoke(StatelessSessionContainer.java:322) at org.jboss.ejb.Container.invoke(Container.java:674) at sun.reflect.GeneratedMethodAccessor36.invoke(Un
Re: Borrow broker from pool failed
Hi Anthony, OJB use a PersistenceBroker instances pool and if enabled a connection pool. In your case the PB-pool seems to be exhausted. This is surprisingly, because per default PB-pool size was 100 and connection-pool size was 20. If you do an query/insert/... operation each PB use a connection, so I would expect that the connection pool will be exhausted before the PB-pool, except somewhere you ask for a PB instance, do not use any DB operation method and forget to close the instance (or use more than 100 concurrent). > I also call broker.close() in the finally clause of every try/catch > block of my data access objects. Should I be calling broker.close() > right after the transaction in the try clause instead of the finally > clause? Using a finally is best practices > I'm using Oracle 8i and only see one active connection to the database, > so the max number of connections are not being exceeded. > This is surprisingly again. > Is there anyway to log how many PersistenceBrokers are in the pool and > if they are being released properly? > Active PB instances can be checked by (undocumented) PersistenceBrokerFactoryFactory.instance().activePersistenceBroker() > If it helps, every time I reload my webapp, the memory usage goes up > and never gets reclaimed. If I get close to the maximum heap, the > program will run out of memory. hmm, don't know if this is caused by OJB. Did your webApp reload all OJB classes and used libraries or only your web classes? regards, Armin Anthony Carlos wrote: Hello OJB gurus: I'm running up against this error message: java.util.NoSuchElementException at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(Generic KeyedObjectPool.java:770) at org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPer sistenceBroker(Unknown Source) at org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.defaultPe rsistenceBroker(Unknown Source) at org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker( Unknown Source) at com.digitalphenom.common.ServiceLocator.findBroker(ServiceLocator.java: 33) ... I found the previous posts regarding this in the following article: http://www.mail-archive.com/[EMAIL PROTECTED]/msg05670.html As the article predicts, I am using ConnectionFactoryPooledImpl and whenExhaustedAction=0 in my OJB.properties file. I also call broker.close() in the finally clause of every try/catch block of my data access objects. Should I be calling broker.close() right after the transaction in the try clause instead of the finally clause? I'm using Oracle 8i and only see one active connection to the database, so the max number of connections are not being exceeded. Is there anyway to log how many PersistenceBrokers are in the pool and if they are being released properly? If it helps, every time I reload my webapp, the memory usage goes up and never gets reclaimed. If I get close to the maximum heap, the program will run out of memory. Thus, I believe that connections are not being released properly. Thanks, -Anthony Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Borrow broker from pool failed
Hello OJB gurus: I'm running up against this error message: java.util.NoSuchElementException at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(Generic KeyedObjectPool.java:770) at org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPer sistenceBroker(Unknown Source) at org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.defaultPe rsistenceBroker(Unknown Source) at org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker( Unknown Source) at com.digitalphenom.common.ServiceLocator.findBroker(ServiceLocator.java: 33) ... I found the previous posts regarding this in the following article: http://www.mail-archive.com/[EMAIL PROTECTED]/msg05670.html As the article predicts, I am using ConnectionFactoryPooledImpl and whenExhaustedAction=0 in my OJB.properties file. I also call broker.close() in the finally clause of every try/catch block of my data access objects. Should I be calling broker.close() right after the transaction in the try clause instead of the finally clause? I'm using Oracle 8i and only see one active connection to the database, so the max number of connections are not being exceeded. Is there anyway to log how many PersistenceBrokers are in the pool and if they are being released properly? If it helps, every time I reload my webapp, the memory usage goes up and never gets reclaimed. If I get close to the maximum heap, the program will run out of memory. Thus, I believe that connections are not being released properly. Thanks, -Anthony Carlos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ERR : Borrow broker from pool failed
Hi,
> When I look in mail-archive, you purpose to close all the
connections, this
> is done with commitTransaction (for PB) or commit() (for ODMG)
> Must I put PB.close() after all connections ?
We have to pools, one for connections (if enabled) and one for PB
instances. Connections are closed on commit or abort - right.
But PB instances closed (return to pool) with
broker.close()
or in older versions of OJB you have to call
PBF.releasePersistenceBroker
(I don't know the exact method name - something similar have a look in
javadoc of PBF/PB).
regards,
Armin
Hennebelle wrote:
Hello,
I have got a big problem with OJB (I think it is OJB),
I have an error : org.apache.ojb.broker.PBFactoryException: Borrow broker
from pool failed
This error comes after 1 or 2 days after the launch of the instance and
comes just after an update (after this error, we can do as select as we want
but we can't make another update). These updates work fine in the beginning
but after a moment (1 or 2 days), no.
I use OJB 0.9.7 with Struts, Oracle 9IAS 9.0.2 and Oracle 8i
In my application, I use ODMG API and PB API.
When I look in mail-archive, you purpose to close all the connections, this
is done with commitTransaction (for PB) or commit() (for ODMG)
Must I put PB.close() after all connections ?
Here is an example of use of ODMG :
TransactionImpl tx = null;
tx = (TransactionImpl) odmg.newTransaction();
tx.begin();
try {
broker = tx.getBroker();
UsrBO usrAM = new UsrBO();
PropertyUtils.copyProperties(usrAM, user);
broker.store(usrAM);
broker.clearCache();
tx.commit();
} catch (Exception e) {
log.error("Error", e);
try {
tx.abort();
} catch (Exception ex) {
log.error("Error 2");
}
throw new DatabaseException(e);
}
Here is an example of use of PB :
try {
broker.beginTransaction();
iterator = broker.getIteratorByQuery(query);
broker.commitTransaction();
} catch (Exception ex) {
log.error("Error", ex);
try {
broker.abortTransaction();
} catch (Exception e) {
log.error("Error 2");
}
throw new DatabaseException(ex);
}
Here is my logs :
497131214 ERROR [ApplicationServerThread-6]
service.PersistanceServicesImpl - Erreur lors de la création / modification
d'un utilisateur :
java.util.NoSuchElementException
at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(Unknown
Source)
at
org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl.createPersisten
ceBroker(Unknown Source)
at
org.apache.ojb.broker.PersistenceBrokerFactory.createPersistenceBroker(Unkno
wn Source)
at org.apache.ojb.odmg.TransactionImpl.getBroker(Unknown Source)
at
aphp.simpa.service.PersistanceServicesImpl.setUtilisateur(PersistanceService
sImpl.java:932)
at aphp.simpa.action.LoginAction.perform(LoginAction.java:404)
at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.ja
va:1787)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:244)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
at
com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.ja
va:59)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
at
com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispa
tcher.java:535)
at
com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletReq
uestDispatcher.java:281)
at
com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandle
r.java:766)
at
com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:152)
at
com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:72)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.ja
va:796)
at java.lang.Thread.run(Thread.java:484)
rethrown as
org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed
at
org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl.createPersisten
ceBroker(Unknown Source)
at
org.apache.ojb.broker.PersistenceBrokerFactory.createPersistenceBroker(Unkno
wn Source)
at org.apache.ojb.odmg.TransactionImpl.getBroker(Unknown Source)
at
aphp.simpa.service.PersistanceServicesImpl.setUtilisateur(PersistanceService
sImpl.java:932)
at aphp.simpa.action.LoginAction.perform(LoginAction.java:404)
at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.ja
va:1787)
at org.apache.struts.action.ActionServlet.process(ActionServlet.ja
ERR : Borrow broker from pool failed
Hello,
I have got a big problem with OJB (I think it is OJB),
I have an error : org.apache.ojb.broker.PBFactoryException: Borrow broker
from pool failed
This error comes after 1 or 2 days after the launch of the instance and
comes just after an update (after this error, we can do as select as we want
but we can't make another update). These updates work fine in the beginning
but after a moment (1 or 2 days), no.
I use OJB 0.9.7 with Struts, Oracle 9IAS 9.0.2 and Oracle 8i
In my application, I use ODMG API and PB API.
When I look in mail-archive, you purpose to close all the connections, this
is done with commitTransaction (for PB) or commit() (for ODMG)
Must I put PB.close() after all connections ?
Here is an example of use of ODMG :
TransactionImpl tx = null;
tx = (TransactionImpl) odmg.newTransaction();
tx.begin();
try {
broker = tx.getBroker();
UsrBO usrAM = new UsrBO();
PropertyUtils.copyProperties(usrAM, user);
broker.store(usrAM);
broker.clearCache();
tx.commit();
} catch (Exception e) {
log.error("Error", e);
try {
tx.abort();
} catch (Exception ex) {
log.error("Error 2");
}
throw new DatabaseException(e);
}
Here is an example of use of PB :
try {
broker.beginTransaction();
iterator = broker.getIteratorByQuery(query);
broker.commitTransaction();
} catch (Exception ex) {
log.error("Error", ex);
try {
broker.abortTransaction();
} catch (Exception e) {
log.error("Error 2");
}
throw new DatabaseException(ex);
}
Here is my logs :
497131214 ERROR [ApplicationServerThread-6]
service.PersistanceServicesImpl - Erreur lors de la création / modification
d'un utilisateur :
java.util.NoSuchElementException
at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(Unknown
Source)
at
org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl.createPersisten
ceBroker(Unknown Source)
at
org.apache.ojb.broker.PersistenceBrokerFactory.createPersistenceBroker(Unkno
wn Source)
at org.apache.ojb.odmg.TransactionImpl.getBroker(Unknown Source)
at
aphp.simpa.service.PersistanceServicesImpl.setUtilisateur(PersistanceService
sImpl.java:932)
at aphp.simpa.action.LoginAction.perform(LoginAction.java:404)
at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.ja
va:1787)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:244)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
at
com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.ja
va:59)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
at
com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispa
tcher.java:535)
at
com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletReq
uestDispatcher.java:281)
at
com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandle
r.java:766)
at
com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:152)
at
com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:72)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.ja
va:796)
at java.lang.Thread.run(Thread.java:484)
rethrown as
org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed
at
org.apache.ojb.broker.ta.PersistenceBrokerFactoryDefaultImpl.createPersisten
ceBroker(Unknown Source)
at
org.apache.ojb.broker.PersistenceBrokerFactory.createPersistenceBroker(Unkno
wn Source)
at org.apache.ojb.odmg.TransactionImpl.getBroker(Unknown Source)
at
aphp.simpa.service.PersistanceServicesImpl.setUtilisateur(PersistanceService
sImpl.java:932)
at aphp.simpa.action.LoginAction.perform(LoginAction.java:404)
at
org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.ja
va:1787)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1586)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:244)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:336)
at
com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.ja
va:59)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
at
com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispa
tcher.java:535)
at
com.evermind.server.http.ServletRequestDispatcher.forwardInter
Re: RE : problem between Broker and org.apache.commons(Borrow broker from pool failed)
Emmanuel Dupont wrote: Maybe you have reach the max number limit of connection borrowed. superfluous to say ... and don't forget to call broker.close() after using a PersistenceBroker instance. This will return pooled PB instance back to pool. regards, Armin In ojb.properties check the flag : ConnectionFactoryClass, it seems you use the ConnectionFactoryPooledImpl And whenExhaustedAction=0 Isn't it ? -Message d'origine- De : Réda Benzair [mailto:[EMAIL PROTECTED] Envoyé : jeudi 30 octobre 2003 13:49 À : 'OJB Users List' Objet : problem between Broker and org.apache.commons(Borrow broker from pool failed) Hi I have a problem in the excecution with this error : Error handled :org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed I do not know which is the cause of this error on the level of OJB. here details of the error : Error handled :org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed at org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPer sistenceBroker(PersistenceBrokerFactoryDefaultImpl.java:238) at org.apache.ojb.broker.PersistenceBrokerFactory.createPersistenceBroker(P ersistenceBrokerFactory.java:129) at cosmos.persistence.CosmosBrokerFactoryImpl.createBroker(CosmosBrokerFact oryImpl.java:63) at sj.employee.handler.EmployeeHandler.findEmployeeById(EmployeeHandler.jav a:44) at sj.mail.MailToTransferDestinator.doAction(Unknown Source) at cosmos.controller.CosmosController.doActions(CosmosController.java:54) at sj._controller.SmartJogController.doActions(SmartJogController.java:84) at cosmos.controller.ControllerDispatcher.performTask(ControllerDispatcher. java:63) at cosmos.CosmosServlet.doTask(CosmosServlet.java:71) at cosmos.InfocenterServlet.doTask(InfocenterServlet.java:86) at cosmos.CosmosServlet.doGet(CosmosServlet.java:80) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241 6) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:263) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:604) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 562) at org.apache.jk.common.SocketConnection.run
RE : problem between Broker and org.apache.commons(Borrow broker from pool failed)
Maybe you have reach the max number limit of connection borrowed. In ojb.properties check the flag : ConnectionFactoryClass, it seems you use the ConnectionFactoryPooledImpl And whenExhaustedAction=0 Isn't it ? -Message d'origine- De : Réda Benzair [mailto:[EMAIL PROTECTED] Envoyé : jeudi 30 octobre 2003 13:49 À : 'OJB Users List' Objet : problem between Broker and org.apache.commons(Borrow broker from pool failed) Hi I have a problem in the excecution with this error : Error handled :org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed I do not know which is the cause of this error on the level of OJB. here details of the error : Error handled :org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed at org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPer sistenceBroker(PersistenceBrokerFactoryDefaultImpl.java:238) at org.apache.ojb.broker.PersistenceBrokerFactory.createPersistenceBroker(P ersistenceBrokerFactory.java:129) at cosmos.persistence.CosmosBrokerFactoryImpl.createBroker(CosmosBrokerFact oryImpl.java:63) at sj.employee.handler.EmployeeHandler.findEmployeeById(EmployeeHandler.jav a:44) at sj.mail.MailToTransferDestinator.doAction(Unknown Source) at cosmos.controller.CosmosController.doActions(CosmosController.java:54) at sj._controller.SmartJogController.doActions(SmartJogController.java:84) at cosmos.controller.ControllerDispatcher.performTask(ControllerDispatcher. java:63) at cosmos.CosmosServlet.doTask(CosmosServlet.java:71) at cosmos.InfocenterServlet.doTask(InfocenterServlet.java:86) at cosmos.CosmosServlet.doGet(CosmosServlet.java:80) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241 6) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:263) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:604) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 562) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:619) at java.lang.Thread.run(Thread.java:536) Caused by: java.util.NoSuchElement
problem between Broker and org.apache.commons(Borrow broker from pool failed)
Hi I have a problem in the excecution with this error : Error handled :org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed I do not know which is the cause of this error on the level of OJB. here details of the error : Error handled :org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed at org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPer sistenceBroker(PersistenceBrokerFactoryDefaultImpl.java:238) at org.apache.ojb.broker.PersistenceBrokerFactory.createPersistenceBroker(P ersistenceBrokerFactory.java:129) at cosmos.persistence.CosmosBrokerFactoryImpl.createBroker(CosmosBrokerFact oryImpl.java:63) at sj.employee.handler.EmployeeHandler.findEmployeeById(EmployeeHandler.jav a:44) at sj.mail.MailToTransferDestinator.doAction(Unknown Source) at cosmos.controller.CosmosController.doActions(CosmosController.java:54) at sj._controller.SmartJogController.doActions(SmartJogController.java:84) at cosmos.controller.ControllerDispatcher.performTask(ControllerDispatcher. java:63) at cosmos.CosmosServlet.doTask(CosmosServlet.java:71) at cosmos.InfocenterServlet.doTask(InfocenterServlet.java:86) at cosmos.CosmosServlet.doGet(CosmosServlet.java:80) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:247) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:193) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:256) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:191) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:241 6) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :180) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa lve.java:171) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :172) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:641) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:174) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.i nvokeNext(StandardPipeline.java:643) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 80) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:263) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:360) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:604) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java: 562) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:679) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool .java:619) at java.lang.Thread.run(Thread.java:536) Caused by: java.util.NoSuchElementException at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(Unknown Source) at org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPer sistenceBroker(PersistenceBrokerFactoryDefaultImpl.java:233) ... 43 more java.util.NoSuchElementException at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(Unknown Source) at
Re: RE: Borrow broker from pool failed
I think I found the problem. I made a mistake when I post my jdbc connection configuration. When this error occurs, there was no autoReconnect=true in the dbalias attribute. Now that I set again this parameter in the dbalias, there is no problem. The connection between MySQL and OJB is correct. Christophe. > Message du 04/07/03 13:52 > De : João Luz <[EMAIL PROTECTED]> > A : OJB Users List <[EMAIL PROTECTED]> > Copie à : > Objet : RE: Borrow broker from pool failed > Try to add validationQuery="select 1" to connection-pool. > > -Original Message- > From: Christophe Marcourt [mailto:[EMAIL PROTECTED] > Sent: quinta-feira, 3 de Julho de 2003 22:29 > To: OJB Users List > Subject: Re: Borrow broker from pool failed > > > I give you as well my connection configuration : > > dbalias="//localhost:3306/housebooking?autoReconnect=true" > default-connection="true" > driver="org.gjt.mm.mysql.Driver" jcd-alias="myConnection" jdbc-level="2.0" > password="" platform="MySQL" > protocol="jdbc" subprotocol="mysql" useAutoCommit="1" > username="christophe"> >maxWait="1" removeAbandoned="true" removeAbandonedTimeout="60"/> >className="org.apache.ojb.broker.util.sequence.SequenceManagerInMemoryImpl"/ > > > > > cheers. > > Christophe > > - Original Message - > From: "Christophe Marcourt" <[EMAIL PROTECTED]> > To: "OJB Users List" <[EMAIL PROTECTED]>; "Armin Waibel" > <[EMAIL PROTECTED]> > Sent: Thursday, July 03, 2003 11:20 PM > Subject: Re: Borrow broker from pool failed > > > > Here you go : > > > > org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed > > 2003-07-03 22:39:51,125 FATAL [Thread-5] - > > > org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersist > > enceBroker(Unknown Source) > > 2003-07-03 22:39:51,125 FATAL [Thread-5] - > > > org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.defaultPersis > > tenceBroker(Unknown Source) > > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > > > org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker(Unkn > > own Source) > > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > > com.hbk.admin.form.RoomParameter.doDefault(RoomParameter.java:152) > > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > > > com.celeno.mandarino.form.AbstractFormDispatch.process(AbstractFormDispatch. > > java:175) > > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > > com.celeno.mandarino.Controller.handleRequest(Controller.java:117) > > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > > > org.apache.velocity.servlet.VelocityServlet.doRequest(VelocityServlet.java:3 > > 72) > > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > > > org.apache.velocity.servlet.VelocityServlet.doGet(VelocityServlet.java:333) > > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > > javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > > > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application > > FilterChain.java:247) > > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > > > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh > > ain.java:193) > > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > > > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja > > va:256) > > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > > eNext(StandardPipeline.java:643) > > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > > > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > > > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja > > va:191) > > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > > > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > > eNext(StandardPipeline.java:643) > > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > > > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase > > .java:494) > &
RE: Borrow broker from pool failed
Try to add validationQuery="select 1" to connection-pool. -Original Message- From: Christophe Marcourt [mailto:[EMAIL PROTECTED] Sent: quinta-feira, 3 de Julho de 2003 22:29 To: OJB Users List Subject: Re: Borrow broker from pool failed I give you as well my connection configuration : cheers. Christophe - Original Message - From: "Christophe Marcourt" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]>; "Armin Waibel" <[EMAIL PROTECTED]> Sent: Thursday, July 03, 2003 11:20 PM Subject: Re: Borrow broker from pool failed > Here you go : > > org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed > 2003-07-03 22:39:51,125 FATAL [Thread-5] - > org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersist > enceBroker(Unknown Source) > 2003-07-03 22:39:51,125 FATAL [Thread-5] - > org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.defaultPersis > tenceBroker(Unknown Source) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker(Unkn > own Source) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > com.hbk.admin.form.RoomParameter.doDefault(RoomParameter.java:152) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > com.celeno.mandarino.form.AbstractFormDispatch.process(AbstractFormDispatch. > java:175) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > com.celeno.mandarino.Controller.handleRequest(Controller.java:117) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > org.apache.velocity.servlet.VelocityServlet.doRequest(VelocityServlet.java:3 > 72) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > org.apache.velocity.servlet.VelocityServlet.doGet(VelocityServlet.java:333) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application > FilterChain.java:247) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh > ain.java:193) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja > va:256) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:643) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja > va:191) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:643) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase > .java:494) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:641) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 > ) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:643) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. > java:171) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:641) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 > ) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:641) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline.invoke(StandardPipel
Re: Borrow broker from pool failed
I give you as well my connection configuration : cheers. Christophe - Original Message - From: "Christophe Marcourt" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]>; "Armin Waibel" <[EMAIL PROTECTED]> Sent: Thursday, July 03, 2003 11:20 PM Subject: Re: Borrow broker from pool failed > Here you go : > > org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed > 2003-07-03 22:39:51,125 FATAL [Thread-5] - > org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersist > enceBroker(Unknown Source) > 2003-07-03 22:39:51,125 FATAL [Thread-5] - > org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.defaultPersis > tenceBroker(Unknown Source) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker(Unkn > own Source) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > com.hbk.admin.form.RoomParameter.doDefault(RoomParameter.java:152) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > com.celeno.mandarino.form.AbstractFormDispatch.process(AbstractFormDispatch. > java:175) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > com.celeno.mandarino.Controller.handleRequest(Controller.java:117) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > org.apache.velocity.servlet.VelocityServlet.doRequest(VelocityServlet.java:3 > 72) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > org.apache.velocity.servlet.VelocityServlet.doGet(VelocityServlet.java:333) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > javax.servlet.http.HttpServlet.service(HttpServlet.java:740) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application > FilterChain.java:247) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh > ain.java:193) > 2003-07-03 22:39:51,126 FATAL [Thread-5] - > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja > va:256) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:643) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja > va:191) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:643) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase > .java:494) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:641) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > 2003-07-03 22:39:51,127 FATAL [Thread-5] - > org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 > ) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:643) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. > java:171) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:641) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 > ) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok > eNext(StandardPipeline.java:641) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) > 2003-07-03 22:39:51,128 FATAL [Thread-5] - > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv
Re: Borrow broker from pool failed
Here you go : org.apache.ojb.broker.PBFactoryException: Borrow broker from pool failed 2003-07-03 22:39:51,125 FATAL [Thread-5] - org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.createPersist enceBroker(Unknown Source) 2003-07-03 22:39:51,125 FATAL [Thread-5] - org.apache.ojb.broker.core.PersistenceBrokerFactoryDefaultImpl.defaultPersis tenceBroker(Unknown Source) 2003-07-03 22:39:51,126 FATAL [Thread-5] - org.apache.ojb.broker.PersistenceBrokerFactory.defaultPersistenceBroker(Unkn own Source) 2003-07-03 22:39:51,126 FATAL [Thread-5] - com.hbk.admin.form.RoomParameter.doDefault(RoomParameter.java:152) 2003-07-03 22:39:51,126 FATAL [Thread-5] - com.celeno.mandarino.form.AbstractFormDispatch.process(AbstractFormDispatch. java:175) 2003-07-03 22:39:51,126 FATAL [Thread-5] - com.celeno.mandarino.Controller.handleRequest(Controller.java:117) 2003-07-03 22:39:51,126 FATAL [Thread-5] - org.apache.velocity.servlet.VelocityServlet.doRequest(VelocityServlet.java:3 72) 2003-07-03 22:39:51,126 FATAL [Thread-5] - org.apache.velocity.servlet.VelocityServlet.doGet(VelocityServlet.java:333) 2003-07-03 22:39:51,126 FATAL [Thread-5] - javax.servlet.http.HttpServlet.service(HttpServlet.java:740) 2003-07-03 22:39:51,126 FATAL [Thread-5] - javax.servlet.http.HttpServlet.service(HttpServlet.java:853) 2003-07-03 22:39:51,126 FATAL [Thread-5] - org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application FilterChain.java:247) 2003-07-03 22:39:51,126 FATAL [Thread-5] - org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh ain.java:193) 2003-07-03 22:39:51,126 FATAL [Thread-5] - org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:256) 2003-07-03 22:39:51,127 FATAL [Thread-5] - org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) 2003-07-03 22:39:51,127 FATAL [Thread-5] - org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 2003-07-03 22:39:51,127 FATAL [Thread-5] - org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 2003-07-03 22:39:51,127 FATAL [Thread-5] - org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:191) 2003-07-03 22:39:51,127 FATAL [Thread-5] - org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) 2003-07-03 22:39:51,127 FATAL [Thread-5] - org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase .java:494) 2003-07-03 22:39:51,127 FATAL [Thread-5] - org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) 2003-07-03 22:39:51,127 FATAL [Thread-5] - org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 2003-07-03 22:39:51,127 FATAL [Thread-5] - org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 2003-07-03 22:39:51,127 FATAL [Thread-5] - org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415) 2003-07-03 22:39:51,128 FATAL [Thread-5] - org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180 ) 2003-07-03 22:39:51,128 FATAL [Thread-5] - org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) 2003-07-03 22:39:51,128 FATAL [Thread-5] - org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve. java:171) 2003-07-03 22:39:51,128 FATAL [Thread-5] - org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) 2003-07-03 22:39:51,128 FATAL [Thread-5] - org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172 ) 2003-07-03 22:39:51,128 FATAL [Thread-5] - org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:641) 2003-07-03 22:39:51,128 FATAL [Thread-5] - org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 2003-07-03 22:39:51,128 FATAL [Thread-5] - org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 2003-07-03 22:39:51,128 FATAL [Thread-5] - org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :174) 2003-07-03 22:39:51,128 FATAL [Thread-5] - org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invok eNext(StandardPipeline.java:643) 2003-07-03 22:39:51,128 FATAL [Thread-5] - org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480) 2003-07-03 22:39:51,129 FATAL [Thread-5] - org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995) 2003-07-03 22:39:51,129 FATAL [Thread-5] - org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223) 2003-07-03 22:39:51,129 FATAL [Thread-5] - org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594) 2003-07-03 22:39:51,129 FATAL [Thread-5] - org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne ction(Http11Protocol.java:392) 2003-07-03 22:39
Re: Borrow broker from pool failed
Can you post the whole stack trace, please? regards, Armin - Original Message - From: "Christophe Marcourt" <[EMAIL PROTECTED]> To: "OJB Users List" <[EMAIL PROTECTED]> Sent: Thursday, July 03, 2003 10:52 PM Subject: Borrow broker from pool failed > Hi, > > after a couple of hours of inactivity I get a "Borrow broker from pool > failed" when I request a page on my site where's OJB make a simple SELECT > query. > I'm using MySQL 4 and OJB 1.0 rc3. > > Any idea ? > > Christophe > > > --- > Ce message Envoi est certifié sans virus connu. > Protégé par l'antivirus AVG Deluxe. > Version: 6.0.492 / Base de données virus: 291 - Date: 24/06/2003 > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Borrow broker from pool failed
Hi, after a couple of hours of inactivity I get a "Borrow broker from pool failed" when I request a page on my site where's OJB make a simple SELECT query. I'm using MySQL 4 and OJB 1.0 rc3. Any idea ? Christophe --- Ce message Envoi est certifié sans virus connu. Protégé par l'antivirus AVG Deluxe. Version: 6.0.492 / Base de données virus: 291 - Date: 24/06/2003 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
