Beware of:   
   PersistenceBroker broker =
PersistenceBrokerFactory.defaultPersistenceBroker();

I ran into some threading issues when using it, after I switched to:
   PersistenceBroker broker =
PersistenceBrokerFactory.createPersistenceBroker(PBKey key)

These problems went away, see an earlier thread "Threadsafety of the
PersistenceBroker default impl"


sg
> -----Original Message-----
> From: Alexander Prozor [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, August 13, 2003 8:15 AM
> To: OJB Users List
> Subject: Re: Connection leak problem with OJB RC3 on Weblogic 7.0 SP2
> 
> 
> :) OJB turorial is not a best source for real applications . 
> it's better to take a look to the unit tests code. as you can 
> see in all tests broker closed:
>             PersistenceBroker broker = 
> PersistenceBrokerFactory.defaultPersistenceBroker();
>             try
>             {
>                    ....
>             }
>             finally
>             {
>                 if (broker != null) broker.close();
>             }
> 
> 
> >Nope, actually I don't call the broker.close() method. Is it 
> necessary? 
> >The example code didn't do that either and the JavaDoc says 
> about the 
> >close()
> >method:
> >"Close this PersistenceBroker so that no further requests 
> may be made on it.
> >A PersistenceBroker instance can be used only until it is 
> closed. Closing a
> >PersistenceBroker might release it to the pool of available
> >PersistenceBrokers, or might be garbage collected, at the 
> option of the
> >implementation. "
> >So it might release the broker instance to the pool, not the 
> connection. Or
> >does it automatically closes the underlying Connection object?
> >
> >I'll give a try anyway.
> >
> >  
> >
> 
> 
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to