openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From davidautentico <davidautent...@hotmail.com>
Subject RE: tomcat6+openjpa+jsf
Date Tue, 01 Jun 2010 12:30:05 GMT

With a derby database also doesnt work, openjpa log:

openjpa.MetaData - "coreservlets.Person" has mapping strategy "full".
3860  person  TRACE  [http-8080-2] openjpa.MetaData - Initializing mapping
for "coreservlets.Person@24177700".
3860  person  TRACE  [http-8080-2] openjpa.MetaData -     Resolving field
"coreservlets.Person@24177700.idPerson".
3860  person  TRACE  [http-8080-2] openjpa.MetaData -     Resolving field
"coreservlets.Person@24177700.mail".
3860  person  TRACE  [http-8080-2] openjpa.MetaData -     Resolving field
"coreservlets.Person@24177700.name".
3969  person  TRACE  [http-8080-2] openjpa.jdbc.SQLDiag - flush:
org.apache.openjpa.kernel.PNewState for oid=null
3985  person  TRACE  [http-8080-2] openjpa.jdbc.JDBC - The batch limit is
set to 0.
4047  person  TRACE  [http-8080-2] openjpa.jdbc.SQL - <t 14949706, conn
12499848> executing prepstmnt 3529877 INSERT INTO persons (id_Person,
e_mail, name) VALUES (?, ?, ?) [params=(long) 1, (String) mail1, (String)
p1]
4078  person  TRACE  [http-8080-2] openjpa.jdbc.SQL - <t 14949706, conn
12499848> [31 ms] spent
4078  person  TRACE  [http-8080-2] openjpa.jdbc.JDBC - <t 14949706, conn
12499848> [0 ms] commit
4078  person  TRACE  [http-8080-2] openjpa.jdbc.JDBC - <t 14949706, conn
12499848> [0 ms] close
4141  person  TRACE  [http-8080-2] openjpa.jdbc.SQLDiag -
getInitializeStateResult: oid=coreservlets.Person-1 class
coreservlets.Person
4188  person  TRACE  [http-8080-2] openjpa.jdbc.SQL - <t 14949706, conn
16938490> executing prepstmnt 16598626 SELECT t0.e_mail, t0.name FROM
persons t0 WHERE t0.id_Person = ? [params=(long) 1]
4203  person  TRACE  [http-8080-2] openjpa.jdbc.SQL - <t 14949706, conn
16938490> [15 ms] spent
4219  person  TRACE  [http-8080-2] openjpa.jdbc.JDBC - <t 14949706, conn
16938490> [0 ms] close
4250  person  TRACE  [http-8080-2] openjpa.jdbc.SQLDiag - flush:
org.apache.openjpa.kernel.PDirtyState for oid=coreservlets.Person-1
4250  person  TRACE  [http-8080-2] openjpa.jdbc.JDBC - The batch limit is
set to 0.
4266  person  TRACE  [http-8080-2] openjpa.jdbc.SQL - <t 14949706, conn
28368430> executing prepstmnt 24691856 UPDATE persons SET e_mail = ? WHERE
id_Person = ? [params=(String) prueba, (long) 0]
4282  person  TRACE  [http-8080-2] openjpa.jdbc.SQL - <t 14949706, conn
28368430> [16 ms] spent
4282  person  TRACE  [http-8080-2] openjpa.Runtime - An exception occurred
while ending the transaction.  This exception will be re-thrown.
<openjpa-2.0.0-r422266:935683 nonfatal store error>
org.apache.openjpa.util.OptimisticException: Optimistic locking errors were
detected when flushing to the data store.  The following objects may have
been concurrently modified in another transaction: [coreservlets.Person-1]
-- 
View this message in context: http://openjpa.208410.n2.nabble.com/tomcat6-openjpa-jsf-tp5120836p5125742.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Mime
View raw message