Is it possible to disable connection pooling in ojb ?
I'm using only one jdbc connection at the same time and do not want
to bother with the validationQuery that is database specific.
Regards,
Guillaume
-
To unsubscribe,
We've done it, but instead of starting from an xsd, we start from an xml and
we generate xsd, repository, torque xml database, java classes aso through
multiple xslt stylesheets.
Regards,
Guillaume
-Message d'origine-
De : David Hooker [mailto:[EMAIL PROTECTED]
Envoye : jeudi 12
Hi Stuart,
Stuart Heriot wrote:
G'day,
I've been testing rc5 and am seeing some unexpected behaviour with regard
cyclic references (eg. ClassA contains a collection of ClassB ojbects.
ClassB contains a reference to a ClassA object.
We have been running with rc4 ok but when we run with rc5,
Original Message
Subject: persistence broker
Date: Thu, 12 Feb 2004 15:33:15 -0600
From: MORRIS, JAMES (CONTRACTOR) [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Thomas,
Is there any way to release a single instance of a persistence broker
that has been closed? I see the
Thank you for your answers, Brendan and Armin!
I'm trying the minEvictableIdleTimeMillis now, set it to 6 - should
that be fine?
Have a good weekend,
Hinnerk
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Thanks, Armin
Guillaume
-Message d'origine-
De : Armin Waibel [mailto:[EMAIL PROTECTED]
Envoye : vendredi 13 fevrier 2004 10:12
A : OJB Users List
Objet : Re: Connection pooling
Hi,
Guillaume Nodet wrote:
Is it possible to disable connection pooling in ojb ?
No
Re-post
-Original Message-
From: Muhammad Aamir
Sent: Wednesday, February 11, 2004 9:51 AM
To: [EMAIL PROTECTED]
Subject: Unique column
There is a column that I want it to be unique in the table. How can I
implement this business rule ??
Thanks
Aamir
Short answer: it's all in documentation. Look there.
Long answer:
As far you have not give more details, just set it as primary key. This guarantee no
duplicates, and no nulls. Don't forget to set this in database too (all good databases
around the world support primary keys).
Other way: in
Hi
when i try to store or retrieve array of object i get this exception (rc5)
java.lang.ClassCastException
at
org.apache.ojb.broker.core.PersistenceBrokerImpl.storeCollections(PersistenceBrokerImpl.java)
i have change the code and it seems to work but is it correct to do that :
in
Hi,
Tino Schöllhorn wrote:
Hi,
I have (again) something weird which I suppose is just a configuration
problem:
I have a class Person which has one LONGVARCHAR-Field. The first time
the object is accessed the LONGVARCHAR-field is returned correctly.
hmm, does this mean first time after
Hello Armin,
I could pinpoint the described error. It all boils to the
QueryFactory.newQuery(Class, Criteria, boolean) method. if I execute the
code to retrieve an instance of class Person with:
Criteria crit = new Criteria();
crit.addEqualTo(id, 85);
Query query =
I'm getting this exception:
Object exists. Instance with the same primary key is already in the
PersistenceManager cache.
javax.jdo.JDOUserException: Object exists. Instance with the same
primary key is already in the PersistenceManager cache.
at
I was right about enhancement and the no-arg constructor. Decompiling my
enhanced class file yields, among other things this:
static
{
jdoPersistenceCapableSuperclass = null;
JDOImplHelper.registerClass(sunjdo$classForName$(org.cs101.fdb.impl.jdo.PersonBase),
jdoFieldNames,
Oops I seem to be experiencing list confusion... if you are looking
back, for the start of this thread and you can't find it that is because
it was a dev list thread. Sorry for the mis-post.
-Gus
Gus Heck wrote:
I was right about enhancement and the no-arg constructor. Decompiling
my
I didn't get any responses yet. Am trying again with more information.
If some guru out there has an answer, I would really appreciate a
response. I'm including a part of the web server logs that shows the
message I am talking about. After a few calls the connections seem to
spontaneously
Hi all.
I just barely started using OJB and have a problem with performance.
I was following The Persistence Broker API tutorial and tried to
retrieve a single record from the database table which contains about
150 rows. It takes 1500ms to execute this query and get the result back!
I am
Hello Oleg,
OJB needs some time perform one-time initialization (load all library classes,
initialize metadata registry, etc).
Execute your test method several times to warm up OJB and JVM before measuring it
performance.
- Original Message -
From: Oleg Lebedev [EMAIL PROTECTED]
To:
Andy,
I ran the query 3 times in a sequence and performance did improve, which
is good news.
I am actually executing this query in 5 concurrent threads. Each thread
performance conforms to the same pattern: first query run takes about
2000 ms, the second run ~ 60ms and the third run is ~ 15ms.
I
Oleg,
Overhead is per-JVM. Warm up OJB before starting multithreaded performance test
(unless you want to test that concurrent
initialization works :-).
I would measure average time instead of single query timing - remember that
System.currentTimeMillis() may not be precise (e.g. on
Windows
Great.
Thanks for your help!
Oleg
-Original Message-
From: Andy Malakov [mailto:[EMAIL PROTECTED]
Sent: Friday, February 13, 2004 4:43 PM
To: OJB Users List
Subject: Re: Slow query via PersistenceBroker
Oleg,
Overhead is per-JVM. Warm up OJB before starting multithreaded
performance
Hi Oleg,
Oleg Lebedev wrote:
Andy,
I ran the query 3 times in a sequence and performance did improve, which
is good news.
I am actually executing this query in 5 concurrent threads. Each thread
performance conforms to the same pattern: first query run takes about
2000 ms, the second run ~ 60ms
21 matches
Mail list logo
