Hi,
Statement batching is really only useful in OpenJPA for transactions
that do a lot of inserts, updates or deletes; it looks like your
workload is entirely select statements.
Also, FYI, if you turn on JDBC logging (vs. SQL logging, which you
already have on), you'll see log messages wh
> -Original Message-
> From: Patrick Linskey [mailto:plins...@gmail.com]
> Sent: Monday, February 01, 2010 3:53 PM
> To: users@openjpa.apache.org
> Subject: Re: How can I tell from debug output whether setting
> "batchLimit" made any difference?
>
> Hi,
>
> Can you post the SQL log for on
Hi,
A SchemaFactory is an interface used by a bunch of JDBC-ish code to
read and modify the current schema, and is pretty bare-bones.
A SchemaGenerator is a class used by the schema creation /
introspection process to convert DB-specific metadata to Schema
objects etc.
Suppose I'm writi
Hi,
Can you post the SQL log for one of your transactions?
-Patrick
On Feb 1, 2010, at 3:44 PM, KARR, DAVID (ATTCINW) wrote:
Normally, when I see a query generate the SQL, OpenJPA prints
performance numbers after each query, like "[15 ms]". I see that on
most of the queries, although some of
Normally, when I see a query generate the SQL, OpenJPA prints
performance numbers after each query, like "[15 ms]". I see that on
most of the queries, although some of them say "[0 ms]".
I decided I wanted to try to turn on statement batching, as several
operations at the transactional layer need
Can someone outline for me what the difference is between these two classes
(other than that SchemaGroup is a class and SchemaFactory is an interface)?
To my eyes they are responsible for the same job.
It also seems like a SchemaGenerator should, in all cases, be a
SchemaFactory.
Suppose I'm wri
Hi,
What's going on in the JVM after the mysql log looks good? I.e., what
happens if you take a thread dump?
Also, can you post your persistence.xml file (or at least the
properties section)? And are you running in an appserver or in a
standalone environment?
-Patrick
On Feb 1, 2010, a
I'm loading a database with over 35,000 records into 100 tables. The tables
may be linked up to 6 levels deep. (Root, A, B, C, X, Y, Z, Root_A, Root_B,
Root_C, A_X, A_Y, B_X, B_Y, B_Z, A_C, B_C, C_Y, C_Z). There is a single root
that contains all the other records (A, B, C). The records contain ot
Hi David,
I'm sure some Spring users monitor this email list, but you might get better
hits on one of the Spring centric lists. It looks like the error originates
in Spring, not OpenJPA.
It's worth checking your compiled classes to make sure they're enhanced
though. Do you have any simple junit s
