Nathan Smith wrote:
I cannot quite remember what the problem was, but it had something to with
Iterators not returning all objects or Collections being returned containing
no objects, but that’s better left for another time at the moment.
Aha, this "smells" like objects of class OJBIterator returne
connections, I think.
Any more suggestions?
> -Original Message-
> From: Martin Kalén [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 24 March 2005 8:56 p.m.
> To: OJB Users List
> Subject: Re: How to shutdown OJB when stopping web context.
>
>
> Greetings all,
&g
Greetings all,
first off - all the different hints of how not to leave open
connections at webapp shutdown (ie using DBCP in Tomcat and supply JNDI
DataSource to OJB, or explicitly calling release methods in OJB at
shutdown) are equally good ways of doing.
Danilo Tommasina wrote:
however it co
Hi,
we use following two calls to shut it down
// Release all persistence broker instances
PersistenceBrokerFactory.releaseAllInstances();
// Release all pooled db connections
ConnectionFactoryFactory.getInstance().createConnectionFactory().releaseAllResources();
however it could be that t
tory.html#releaseAllResources()
e.g.
ConnectionFactoryFactory.getInstance().createFactory().releaseAllResources()
;
Cheers
Charles
-Original Message-
From: Alexandre Borgoltz [mailto:[EMAIL PROTECTED]
Sent: 24 March 2005 07:27
To: OJB Users List
Subject: Re: How to shutdown OJB when stopping
Nathan,
I can see you aren't getting any answer for a few hours so I'll dare my
own hint...
Maybe you could have OJB use a container-provided datasource instead.
For this, use jndi-datasource-name instead of
dbalias/driver/user/password/protocol/subprotocol in your
http://db.apache.org/ojb/doc
