Hi, thanks for all the help - the whole thing was actually caused by the lack of the cleanup code (broker.close()). Now everything works fine!
/peter On Sat, 2002-09-07 at 13:29, Armin Waibel wrote: > >org.apache.ojb.broker.accesslayer.ConnectioFactoryConPooledImpl.lookup > Strange I could not find such a method? > Which version do you use? > > We have a separate pool for connection pooling in OJB (we pool PB > instances and connections in different pools). > In OJB.properties you can configure the default connection pool size > with > maxConnectionsInPool=21 > The default behaviour of the connection pool is to throw a exception if > the pool is exhausted (you can explicit configure each connection pool > in the repository.xml, see repository.dtd), thus the OJB connection pool > is not exhausted, rather the pool try to obtain a new connection from > your DBMS and wait for response. > Try to increase the max active connections of your DBMS, or try to > reduce the maxConnectionsInPool-property to see if a exception arise. > > regards, > Armin > > ----- Original Message ----- > From: "Peter Neubauer" <[EMAIL PROTECTED]> > To: "OJB Users List" <[EMAIL PROTECTED]> > Sent: Saturday, September 07, 2002 12:15 PM > Subject: Re: OJB stopping to work > > > Now I have debugged a bit and it seems that OJB is waiting for the > org.apache.commons.pool.impl.GenericObjectPool.wait() > org.apache.commons.pool.impl.GenericObjectPool.borrowObject() > org.apache.ojb.broker.accesslayer.ConnectioFactoryConPooledImpl.lookup() > > So it should be that the connectionpool gets exhausted. But the > application seems to wait anyway. That is in spite of > > # specifies the behaviour of the pool when broker capacity is > # exhausted (see maxActive above) > # 0 - fail > # 1 - block > # 2 - grow > whenExhaustedAction=0 > > in OJB.properties. Shouldn't the pool raise an exeption then? > > After all logs are set to DEBUG, there are no more SQL statements > coming. > > > Thanks for the help > > /peter > > > stop comes in On Sat, 2002-09-07 at 11:02, Thomas Mahler wrote: > > Please try to set all loglevel to DEBUG to see if there is no more OJB > > activity. > > > > Activate the P6Spy (setup explained in FAQ) to check if there is no > more > > SQL activity from OJB > > > > The OJB caches uses weak-references, thus they are fully > > garbage-collectable. So I can't believe it is a caching problem. > > > > cheers, > > Thomas > > > > Peter Neubauer wrote: > > > Hi, > > > I get a very strabge behavior with OJB. Some time after I have > started > > > my tubine application, OJB seems just to stop to work, without any > > > error. Are there any caches getting full? > > > > > > Has anyone had some similar problem? > > > > > > /peter > > > > > > _____________________________________________________ > > > F�lj VM p� n�ra h�ll p� Yahoo!s officielle VM-sajt > www.yahoo.se/vm2002 > > > H�ll dig ajour med nyheter och resultat, med vinnare och > f�rlorare... > > > > > > -- > > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > _____________________________________________________ > > F�lj VM p� n�ra h�ll p� Yahoo!s officielle VM-sajt www.yahoo.se/vm2002 > > H�ll dig ajour med nyheter och resultat, med vinnare och f�rlorare... > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> _____________________________________________________ Gratis e-mail resten av livet p� www.yahoo.se/mail Busenkelt! -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
