| [Teneo] Bug in JPOX(CORE-3356) - fixed with the 1.2.0-beta-4. Will Teneo support it? [message #610010] |
Mon, 15 October 2007 19:24 |
 Vladimir Nikolov
Messages: 10
Registered: July 2009 |
Junior Member |
|
|
Hello,
I'm using Teneo/JPOX and I'm experiencing the following problem.
When I delete an object in a transaction, on transaction commit the
Teneo/JPOX tries to fetch all data from the database including the
objects already deleted during the transaction.
For example:
Transaction tx = pmc.getPM().currentTransaction();
tx.begin();
//....
//some code which marks persistent capable objects to be deleted on
resource.save()
//....
resource1.save(new HashMap());
resource2.save(new HashMap());
tx.commit();
A JDOObjectNotFoundException is thrown. Here is a sample of the log:
when resource.save() is executed the log is:
17:17:29,281 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
"book1" : P_CLEAN->P_DELETED
17:17:29,281 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO] - Deleting
object com.mylibrary.Book@1396855618 of type com.mylibrary.Book from
table BOOK
17:17:29,281 (SoapConnectorThreadPool : 2) DEBUG [JPOX.RDBMS.SQL] -
DELETE FROM BOOKWHERE BOOKID = <'book1'>
17:17:29,594 (SoapConnectorThreadPool : 2) DEBUG [JPOX.RDBMS.SQL] -
Execution Time = 313 ms
When tx.comit() is executed the log is:
17:18:30,878 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO] - Fetching
class com.mylibrary.Book fields [bookID,title] for object book1 in table
BOOK
17:18:30,878 (SoapConnectorThreadPool : 2) DEBUG [JPOX.RDBMS.SQL] -
SELECT THIS.BOOKID,THIS.E_VERSION,THIS.TITLE FROM BOOK THIS WHERE
(THIS.BOOKID=<'book1'>)
17:18:30,878 (SoapConnectorThreadPool : 2) DEBUG [JPOX.RDBMS.SQL] -
Execution Time = 0 ms
17:18:30,878 (SoapConnectorThreadPool : 2) WARN [JPOX.RDBMS.SQL] -
Object with id "book1" not found !
While I was investigating I found that the same(or at least similar)
problem has been found by other developers and it is considered as an
JPOX bug. Here is a link to the JIRA:
http://www.jpox.org/servlet/jira/browse/CORE-3356?page=com.a tlassian.jira.plugin.system.issuetabpanels:all-tabpanel
This problem is fixed with 1.2.0-beta-4 JPOX version. However, the
latest JPOX version which Teneo supports is JPOX 1.1.8.
Will Teneo soon support the new version of JPOX? Or is there any way
that I can use this new beta jpox version with current Teneo version?
Or maybe any hint to workaround the problem?
Any help will be appreciated!
Regards,
Vladimir Nikolov
|
|
|
Powered by
FUDForum. Page generated in 0.02222 seconds
] 
Search
Help
Register
Login
Home
