openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mysakjs <my...@us.ibm.com>
Subject Re: record delete during flo
Date Fri, 12 Jul 2013 04:41:03 GMT
Please ignore the above exception.   That is most likely occurring when I had
the database user DELETE permissions revoked to see where an exception might
be thrown, to better understand what is causing the seemingly phantom DELETE
activity (after a SELECT).   

The thing interesting is the SELECT query , that results in a subsequent
unexpected and unwanted DELETE (for no apparent reason) has a lot of LEFT
OUTER JOINS due to EAGER fetching of data in 1 : many relationships.   It
appears from the openjpa trace there's about 6 of them.  (left outer joins).  
I don't know if that could be contributing to the problem and I wouldn't
think so, but I thought I'd mention it anyway.

Here's all that seems to be logged in the openjpa trace all (in WAS 8.5)
when the unwanted DELETE is occuring, when the permissions are restored and
the db user is allowed to DELETE:

[7/12/13 0:29:27:681 EDT] 0000009d OpenJPA       3   openjpa.jdbc.JDBC:
Trace: <t 922525506, conn 500988834> [0 ms] close
[7/12/13 0:29:27:682 EDT] 0000009d OpenJPA       3   openjpa.jdbc.SQLDiag:
Trace: flush: org.apache.openjpa.kernel.PDirtyState for oid=103546
[7/12/13 0:29:27:682 EDT] 0000009d OpenJPA       3   openjpa.jdbc.JDBC:
Trace: The batch limit is set to 100.
[7/12/13 0:29:27:682 EDT] 0000009d OpenJPA       3   openjpa.jdbc.JDBC:
Trace: <t 922525506, conn 190483185> [0 ms] close

Not sure if this provides any clues, but I'll search on it.    In addition
to PDirtyState  I have also seen messages logged for PDeletedState... right
before the DELETE happens.

[7/12/13 0:27:55:527 EDT] 00000099 OpenJPA       3   openjpa.jdbc.SQLDiag:
Trace: flush: org.apache.openjpa.kernel.PDirtyState for oid=103541
[7/12/13 0:27:55:527 EDT] 00000099 OpenJPA       3   openjpa.jdbc.SQLDiag:
Trace: flush: org.apache.openjpa.kernel.PDeletedState for oid=51850
[7/12/13 0:27:55:528 EDT] 00000099 OpenJPA       3   openjpa.jdbc.JDBC:
Trace: The batch limit is set to 100.
[7/12/13 0:27:55:528 EDT] 00000099 OpenJPA       3   openjpa.jdbc.SQL:
Trace: <t 391662123, conn -22357016> executing prepstmnt -1292669644 DELETE
FROM <table_name> WHERE id = ? [params=?]




--
View this message in context: http://openjpa.208410.n2.nabble.com/record-delete-during-flo-tp7584399p7584400.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.

Mime
View raw message