,
Armin
- Original Message -
From: Gustafson, Scott F. [EMAIL PROTECTED]
To: OJB Users List [EMAIL PROTECTED]
Sent: Wednesday, August 13, 2003 2:25 PM
Subject: RE: Connection leak problem with OJB RC3 on Weblogic 7.0 SP2
Beware of:
PersistenceBroker broker
?
I'll give a try anyway.
-Original Message-
From: Alexander Prozor [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 13, 2003 1:49 PM
To: OJB Users List
Subject: Re: Connection leak problem with OJB RC3 on Weblogic 7.0 SP2
Do you call
broker.clcse() method after storing/retriaving
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
Hi,
I have got a problem with using OJB RC3 on Weblogic 7.0 SP2.
In the Weblogic there's a connection pool and datasource set up. The OJB is
connecting to the database via this JNDI Datasource. No matter which
ConnectionFactoryClass I set in the OJB.properties, I always get a
connection leak
ups, typos
- Original Message -
From: Armin Waibel [EMAIL PROTECTED]
To: OJB Users List [EMAIL PROTECTED]
Sent: Wednesday, August 13, 2003 2:51 PM
Subject: Re: Connection leak problem with OJB RC3 on Weblogic 7.0 SP2
Hi,
there is no difference in intern handling between
Do you call
broker.clcse() method after storing/retriaving operations?
Hi,
I have got a problem with using OJB RC3 on Weblogic 7.0 SP2.
In the Weblogic there's a connection pool and datasource set up. The OJB is
connecting to the database via this JNDI Datasource. No matter which
Thanks Alexander, it seems that was indeed the problem.
-Original Message-
From: Alexander Prozor [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 13, 2003 2:15 PM
To: OJB Users List
Subject: Re: Connection leak problem with OJB RC3 on Weblogic 7.0 SP2
:) OJB turorial is not a best
:) 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
{
When will we see some *real* documentation? I've got a pretty big
application that's being planned out now that will (hopefully) use OJB,
and some real-world documentation would be nice :)
-Clay
Armin Waibel wrote:
:) OJB turorial is not a best source for real applications .
Currently Brain
