Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » [Teneo] Bug in JPOX(CORE-3356) - fixed with the 1.2.0-beta-4. Will Teneo support it?
| [Teneo] Bug in JPOX(CORE-3356) - fixed with the 1.2.0-beta-4. Will Teneo support it? [message #99179] |
Mon, 15 October 2007 19:24  |
Eclipse User |
|
|
|
Originally posted by: vnikolov.us.ibm.com
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
|
|
|
| Re: [Teneo] Bug in JPOX(CORE-3356) - fixed with the 1.2.0-beta-4. Will Teneo support it? [message #99197 is a reply to message #99179] |
Mon, 15 October 2007 21:30  |
 Martin Taal
Messages: 5468
Registered: July 2009 |
Senior Member |
|
|
Hi Vladimir,
As teneo uses some internal jpox api's it won't work with jpox 1.2. I won't have time to upgrade to
jpox 1.2 in the short term, so it will be at least a month.
Looking at the log only a warning is logged so afaics the transaction commits ok. Or does the
transaction fail?
gr. Martin
Vladimir Nikolov wrote:
> 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
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
| Re: [Teneo] Bug in JPOX(CORE-3356) - fixed with the 1.2.0-beta-4. Will Teneo support it? [message #99243 is a reply to message #99197] |
Tue, 16 October 2007 13:56 |
| Eclipse User |
|
|
|
Originally posted by: vnikolov.us.ibm.com
Hello Martin,
Thanks for answering.
Im my case the transaction is failed. That seems to be the only
difference with the JIRA I refered to from my previous post.
I'm using Persistence Manager Controller, the transaction is
pessimistic, the isolation level is READ_COMMITTED. I'm using DB2.
Here is a more extended part of the JPOX log on tx.comit():
.....
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 !
17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
"16[OID]com.mylibrary.Author" : P_CLEAN->HOLLOW
17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
"16[OID]com.mylibrary.Author" : evicting from transactional cache
17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
"13[OID]com.mylibrary.Publisher" : P_CLEAN->HOLLOW
17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
"13[OID]com.mylibrary.Publisher" : evicting from transactional cache
17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
"_-1131670256" : P_CLEAN->HOLLOW
17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
"_-1131670256" : evicting from transactional cache
......
17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
"_-1595112348" : P_DELETED->P_NONTRANS
17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
"_-1595112348" : evicting from transactional cache
......
17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
"book1" : P_DELETED->P_NONTRANS
17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
"book1" : evicting from transactional cache
......
and so on..
All objects which state have been changed to P_DELETED on
resource.save() are set back from P_DELETE to P_NONTRANS after the warning.
Here is the exception stack trace from my server's log:
------Start of DE processing------ = [07-10-15 17:55:57:177 EEST] , key
= javax.jdo.JDOObjectNotFoundException myClass.myMethod() 1001
Exception = javax.jdo.JDOObjectNotFoundException
Source = myClass.myMethod()
probeid = 1001
Stack Dump = javax.jdo.JDOObjectNotFoundException: No such database row
FailedObject:book1
at org.jpox.store.rdbms.request.FetchRequest.execute(FetchReque st.java:194)
at org.jpox.store.rdbms.table.ClassTable.fetch(ClassTable.java: 2552)
at org.jpox.store.StoreManager.fetch(StoreManager.java:959)
at
org.jpox.state.StateManagerImpl.loadUnloadedFieldsInFetchPla n(StateManagerImpl.java:1842)
at
org.jpox.state.StateManagerImpl.loadFieldsInFetchPlan(StateM anagerImpl.java:1796)
at
org.eclipse.emf.teneo.jpox.elist.EListWrapper.loadFieldsInFe tchPlan(EListWrapper.java:825)
at
org.jpox.state.LoadFieldManager.internalFetchObjectField(Loa dFieldManager.java:82)
at
org.jpox.state.AbstractFetchFieldManager.fetchObjectField(Ab stractFetchFieldManager.java:108)
at
org.jpox.state.StateManagerImpl.replacingObjectField(StateMa nagerImpl.java:2951)
at com.mylibrary.Books.jdoReplaceField(Books.java)
at com.mylibrary.Books.jdoReplaceFields(Books.java)
at
org.jpox.state.StateManagerImpl.replaceFields(StateManagerIm pl.java:3170)
at
org.jpox.state.StateManagerImpl.replaceFields(StateManagerIm pl.java:3188)
at
org.jpox.state.StateManagerImpl.loadFieldsInFetchPlan(StateM anagerImpl.java:1803)
at
org.jpox.AbstractPersistenceManager.preCommit(AbstractPersis tenceManager.java:3447)
at
org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit(RDBMS NonmanagedTransaction.java:400)
at com.myClass.myMethod()(myClass.java:101)
Do you have any ideas why my transaction fails? Is there any way that I
can restrain my transaction from failing like the case in the JIRA?
The transaction I'm using is from
org.eclipse.emf.teneo.jpox.resource.PMController.
Regards,
Vladimir Nikolov
Martin Taal wrote:
> Hi Vladimir,
> As teneo uses some internal jpox api's it won't work with jpox 1.2. I
> won't have time to upgrade to jpox 1.2 in the short term, so it will be
> at least a month.
> Looking at the log only a warning is logged so afaics the transaction
> commits ok. Or does the transaction fail?
>
> gr. Martin
>
> Vladimir Nikolov wrote:
>> 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
>
>
|
|
|
| Re: [Teneo] Bug in JPOX(CORE-3356) - fixed with the 1.2.0-beta-4. Will Teneo support it? [message #99292 is a reply to message #99243] |
Tue, 16 October 2007 19:52 |
Martin Taal
Messages: 5468
Registered: July 2009 |
Senior Member |
|
|
Hi Vladimir,
No I don't know why your transaction fails while the jpox jira mentions that it does not fail. The
jira is also for jpox 1.2, while Teneo uses 1.1.8. So this can explain different behavior.
Have you tried to set the option:
org.jpox.persistenceByReachabilityAtCommit
to false?
gr. Martin
Vladimir Nikolov wrote:
> Hello Martin,
> Thanks for answering.
> Im my case the transaction is failed. That seems to be the only
> difference with the JIRA I refered to from my previous post.
> I'm using Persistence Manager Controller, the transaction is
> pessimistic, the isolation level is READ_COMMITTED. I'm using DB2.
>
> Here is a more extended part of the JPOX log on tx.comit():
> .....
> 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 !
> 17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
> "16[OID]com.mylibrary.Author" : P_CLEAN->HOLLOW
> 17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
> "16[OID]com.mylibrary.Author" : evicting from transactional cache
> 17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
> "13[OID]com.mylibrary.Publisher" : P_CLEAN->HOLLOW
> 17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
> "13[OID]com.mylibrary.Publisher" : evicting from transactional cache
> 17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
> "_-1131670256" : P_CLEAN->HOLLOW
> 17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
> "_-1131670256" : evicting from transactional cache
> ......
> 17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
> "_-1595112348" : P_DELETED->P_NONTRANS
> 17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
> "_-1595112348" : evicting from transactional cache
> ......
> 17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
> "book1" : P_DELETED->P_NONTRANS
> 17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
> "book1" : evicting from transactional cache
> ......
> and so on..
>
> All objects which state have been changed to P_DELETED on
> resource.save() are set back from P_DELETE to P_NONTRANS after the warning.
>
> Here is the exception stack trace from my server's log:
> ------Start of DE processing------ = [07-10-15 17:55:57:177 EEST] , key
> = javax.jdo.JDOObjectNotFoundException myClass.myMethod() 1001
> Exception = javax.jdo.JDOObjectNotFoundException
> Source = myClass.myMethod()
> probeid = 1001
> Stack Dump = javax.jdo.JDOObjectNotFoundException: No such database row
> FailedObject:book1
> at
> org.jpox.store.rdbms.request.FetchRequest.execute(FetchReque st.java:194)
> at org.jpox.store.rdbms.table.ClassTable.fetch(ClassTable.java: 2552)
> at org.jpox.store.StoreManager.fetch(StoreManager.java:959)
> at
> org.jpox.state.StateManagerImpl.loadUnloadedFieldsInFetchPla n(StateManagerImpl.java:1842)
>
> at
> org.jpox.state.StateManagerImpl.loadFieldsInFetchPlan(StateM anagerImpl.java:1796)
>
> at
> org.eclipse.emf.teneo.jpox.elist.EListWrapper.loadFieldsInFe tchPlan(EListWrapper.java:825)
>
> at
> org.jpox.state.LoadFieldManager.internalFetchObjectField(Loa dFieldManager.java:82)
>
> at
> org.jpox.state.AbstractFetchFieldManager.fetchObjectField(Ab stractFetchFieldManager.java:108)
>
> at
> org.jpox.state.StateManagerImpl.replacingObjectField(StateMa nagerImpl.java:2951)
>
> at com.mylibrary.Books.jdoReplaceField(Books.java)
> at com.mylibrary.Books.jdoReplaceFields(Books.java)
> at
> org.jpox.state.StateManagerImpl.replaceFields(StateManagerIm pl.java:3170)
> at
> org.jpox.state.StateManagerImpl.replaceFields(StateManagerIm pl.java:3188)
> at
> org.jpox.state.StateManagerImpl.loadFieldsInFetchPlan(StateM anagerImpl.java:1803)
>
> at
> org.jpox.AbstractPersistenceManager.preCommit(AbstractPersis tenceManager.java:3447)
>
> at
> org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit(RDBMS NonmanagedTransaction.java:400)
>
> at com.myClass.myMethod()(myClass.java:101)
>
>
> Do you have any ideas why my transaction fails? Is there any way that I
> can restrain my transaction from failing like the case in the JIRA?
> The transaction I'm using is from
> org.eclipse.emf.teneo.jpox.resource.PMController.
>
> Regards,
> Vladimir Nikolov
>
>
> Martin Taal wrote:
>> Hi Vladimir,
>> As teneo uses some internal jpox api's it won't work with jpox 1.2. I
>> won't have time to upgrade to jpox 1.2 in the short term, so it will
>> be at least a month.
>> Looking at the log only a warning is logged so afaics the transaction
>> commits ok. Or does the transaction fail?
>>
>> gr. Martin
>>
>> Vladimir Nikolov wrote:
>>> 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
>>
>>
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
| Re: [Teneo] Bug in JPOX(CORE-3356) - fixed with the 1.2.0-beta-4. Will Teneo support it? [message #99347 is a reply to message #99292] |
Wed, 17 October 2007 09:20 |
| Eclipse User |
|
|
|
Originally posted by: vnikolov.us.ibm.com
Hello Martin,
I've managed to fix my problem. The reason for it was different from the
one I initially suspected. It was related with detachAllOnCommit settings.
Thanks for your time and your guidelines. They really helped me in
finding the real roots of the problem.
Greetings,
Vladimir
Martin Taal wrote:
> Hi Vladimir,
> No I don't know why your transaction fails while the jpox jira mentions
> that it does not fail. The jira is also for jpox 1.2, while Teneo uses
> 1.1.8. So this can explain different behavior.
>
> Have you tried to set the option:
> org.jpox.persistenceByReachabilityAtCommit
> to false?
>
> gr. Martin
>
|
|
|
| Re: [Teneo] Bug in JPOX(CORE-3356) - fixed with the 1.2.0-beta-4. Will Teneo support it? [message #610013 is a reply to message #99179] |
Mon, 15 October 2007 21:30 |
Martin Taal
Messages: 5468
Registered: July 2009 |
Senior Member |
|
|
Hi Vladimir,
As teneo uses some internal jpox api's it won't work with jpox 1.2. I won't have time to upgrade to
jpox 1.2 in the short term, so it will be at least a month.
Looking at the log only a warning is logged so afaics the transaction commits ok. Or does the
transaction fail?
gr. Martin
Vladimir Nikolov wrote:
> 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
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
|
| Re: [Teneo] Bug in JPOX(CORE-3356) - fixed with the 1.2.0-beta-4. Will Teneo support it? [message #610021 is a reply to message #99197] |
Tue, 16 October 2007 13:56 |
Vladimir Nikolov
Messages: 10
Registered: July 2009 |
Junior Member |
|
|
Hello Martin,
Thanks for answering.
Im my case the transaction is failed. That seems to be the only
difference with the JIRA I refered to from my previous post.
I'm using Persistence Manager Controller, the transaction is
pessimistic, the isolation level is READ_COMMITTED. I'm using DB2.
Here is a more extended part of the JPOX log on tx.comit():
.....
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 !
17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
"16[OID]com.mylibrary.Author" : P_CLEAN->HOLLOW
17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
"16[OID]com.mylibrary.Author" : evicting from transactional cache
17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
"13[OID]com.mylibrary.Publisher" : P_CLEAN->HOLLOW
17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
"13[OID]com.mylibrary.Publisher" : evicting from transactional cache
17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
"_-1131670256" : P_CLEAN->HOLLOW
17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
"_-1131670256" : evicting from transactional cache
......
17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
"_-1595112348" : P_DELETED->P_NONTRANS
17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
"_-1595112348" : evicting from transactional cache
......
17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
"book1" : P_DELETED->P_NONTRANS
17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
"book1" : evicting from transactional cache
......
and so on..
All objects which state have been changed to P_DELETED on
resource.save() are set back from P_DELETE to P_NONTRANS after the warning.
Here is the exception stack trace from my server's log:
------Start of DE processing------ = [07-10-15 17:55:57:177 EEST] , key
= javax.jdo.JDOObjectNotFoundException myClass.myMethod() 1001
Exception = javax.jdo.JDOObjectNotFoundException
Source = myClass.myMethod()
probeid = 1001
Stack Dump = javax.jdo.JDOObjectNotFoundException: No such database row
FailedObject:book1
at org.jpox.store.rdbms.request.FetchRequest.execute(FetchReque st.java:194)
at org.jpox.store.rdbms.table.ClassTable.fetch(ClassTable.java: 2552)
at org.jpox.store.StoreManager.fetch(StoreManager.java:959)
at
org.jpox.state.StateManagerImpl.loadUnloadedFieldsInFetchPla n(StateManagerImpl.java:1842)
at
org.jpox.state.StateManagerImpl.loadFieldsInFetchPlan(StateM anagerImpl.java:1796)
at
org.eclipse.emf.teneo.jpox.elist.EListWrapper.loadFieldsInFe tchPlan(EListWrapper.java:825)
at
org.jpox.state.LoadFieldManager.internalFetchObjectField(Loa dFieldManager.java:82)
at
org.jpox.state.AbstractFetchFieldManager.fetchObjectField(Ab stractFetchFieldManager.java:108)
at
org.jpox.state.StateManagerImpl.replacingObjectField(StateMa nagerImpl.java:2951)
at com.mylibrary.Books.jdoReplaceField(Books.java)
at com.mylibrary.Books.jdoReplaceFields(Books.java)
at
org.jpox.state.StateManagerImpl.replaceFields(StateManagerIm pl.java:3170)
at
org.jpox.state.StateManagerImpl.replaceFields(StateManagerIm pl.java:3188)
at
org.jpox.state.StateManagerImpl.loadFieldsInFetchPlan(StateM anagerImpl.java:1803)
at
org.jpox.AbstractPersistenceManager.preCommit(AbstractPersis tenceManager.java:3447)
at
org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit(RDBMS NonmanagedTransaction.java:400)
at com.myClass.myMethod()(myClass.java:101)
Do you have any ideas why my transaction fails? Is there any way that I
can restrain my transaction from failing like the case in the JIRA?
The transaction I'm using is from
org.eclipse.emf.teneo.jpox.resource.PMController.
Regards,
Vladimir Nikolov
Martin Taal wrote:
> Hi Vladimir,
> As teneo uses some internal jpox api's it won't work with jpox 1.2. I
> won't have time to upgrade to jpox 1.2 in the short term, so it will be
> at least a month.
> Looking at the log only a warning is logged so afaics the transaction
> commits ok. Or does the transaction fail?
>
> gr. Martin
>
> Vladimir Nikolov wrote:
>> 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
>
>
|
|
|
| Re: [Teneo] Bug in JPOX(CORE-3356) - fixed with the 1.2.0-beta-4. Will Teneo support it? [message #610030 is a reply to message #99243] |
Tue, 16 October 2007 19:52 |
Martin Taal
Messages: 5468
Registered: July 2009 |
Senior Member |
|
|
Hi Vladimir,
No I don't know why your transaction fails while the jpox jira mentions that it does not fail. The
jira is also for jpox 1.2, while Teneo uses 1.1.8. So this can explain different behavior.
Have you tried to set the option:
org.jpox.persistenceByReachabilityAtCommit
to false?
gr. Martin
Vladimir Nikolov wrote:
> Hello Martin,
> Thanks for answering.
> Im my case the transaction is failed. That seems to be the only
> difference with the JIRA I refered to from my previous post.
> I'm using Persistence Manager Controller, the transaction is
> pessimistic, the isolation level is READ_COMMITTED. I'm using DB2.
>
> Here is a more extended part of the JPOX log on tx.comit():
> .....
> 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 !
> 17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
> "16[OID]com.mylibrary.Author" : P_CLEAN->HOLLOW
> 17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
> "16[OID]com.mylibrary.Author" : evicting from transactional cache
> 17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
> "13[OID]com.mylibrary.Publisher" : P_CLEAN->HOLLOW
> 17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
> "13[OID]com.mylibrary.Publisher" : evicting from transactional cache
> 17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
> "_-1131670256" : P_CLEAN->HOLLOW
> 17:18:30,893 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
> "_-1131670256" : evicting from transactional cache
> ......
> 17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
> "_-1595112348" : P_DELETED->P_NONTRANS
> 17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
> "_-1595112348" : evicting from transactional cache
> ......
> 17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.JDO.Lifecycle] -
> "book1" : P_DELETED->P_NONTRANS
> 17:18:30,909 (SoapConnectorThreadPool : 2) DEBUG [JPOX.Transaction] -
> "book1" : evicting from transactional cache
> ......
> and so on..
>
> All objects which state have been changed to P_DELETED on
> resource.save() are set back from P_DELETE to P_NONTRANS after the warning.
>
> Here is the exception stack trace from my server's log:
> ------Start of DE processing------ = [07-10-15 17:55:57:177 EEST] , key
> = javax.jdo.JDOObjectNotFoundException myClass.myMethod() 1001
> Exception = javax.jdo.JDOObjectNotFoundException
> Source = myClass.myMethod()
> probeid = 1001
> Stack Dump = javax.jdo.JDOObjectNotFoundException: No such database row
> FailedObject:book1
> at
> org.jpox.store.rdbms.request.FetchRequest.execute(FetchReque st.java:194)
> at org.jpox.store.rdbms.table.ClassTable.fetch(ClassTable.java: 2552)
> at org.jpox.store.StoreManager.fetch(StoreManager.java:959)
> at
> org.jpox.state.StateManagerImpl.loadUnloadedFieldsInFetchPla n(StateManagerImpl.java:1842)
>
> at
> org.jpox.state.StateManagerImpl.loadFieldsInFetchPlan(StateM anagerImpl.java:1796)
>
> at
> org.eclipse.emf.teneo.jpox.elist.EListWrapper.loadFieldsInFe tchPlan(EListWrapper.java:825)
>
> at
> org.jpox.state.LoadFieldManager.internalFetchObjectField(Loa dFieldManager.java:82)
>
> at
> org.jpox.state.AbstractFetchFieldManager.fetchObjectField(Ab stractFetchFieldManager.java:108)
>
> at
> org.jpox.state.StateManagerImpl.replacingObjectField(StateMa nagerImpl.java:2951)
>
> at com.mylibrary.Books.jdoReplaceField(Books.java)
> at com.mylibrary.Books.jdoReplaceFields(Books.java)
> at
> org.jpox.state.StateManagerImpl.replaceFields(StateManagerIm pl.java:3170)
> at
> org.jpox.state.StateManagerImpl.replaceFields(StateManagerIm pl.java:3188)
> at
> org.jpox.state.StateManagerImpl.loadFieldsInFetchPlan(StateM anagerImpl.java:1803)
>
> at
> org.jpox.AbstractPersistenceManager.preCommit(AbstractPersis tenceManager.java:3447)
>
> at
> org.jpox.store.rdbms.RDBMSNonmanagedTransaction.commit(RDBMS NonmanagedTransaction.java:400)
>
> at com.myClass.myMethod()(myClass.java:101)
>
>
> Do you have any ideas why my transaction fails? Is there any way that I
> can restrain my transaction from failing like the case in the JIRA?
> The transaction I'm using is from
> org.eclipse.emf.teneo.jpox.resource.PMController.
>
> Regards,
> Vladimir Nikolov
>
>
> Martin Taal wrote:
>> Hi Vladimir,
>> As teneo uses some internal jpox api's it won't work with jpox 1.2. I
>> won't have time to upgrade to jpox 1.2 in the short term, so it will
>> be at least a month.
>> Looking at the log only a warning is logged so afaics the transaction
>> commits ok. Or does the transaction fail?
>>
>> gr. Martin
>>
>> Vladimir Nikolov wrote:
>>> 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
>>
>>
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@springsite.com - mtaal@elver.org
Web: www.springsite.com - www.elver.org
|
|
| |
Goto Forum:
Current Time: Sat Nov 09 01:51:18 GMT 2024
Powered by FUDForum. Page generated in 0.03483 seconds |
] 
Search
Help
Register
Login
Home
