Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0032309
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Openbravo ERP] A. Platformmajorhave not tried2016-02-23 10:552016-02-24 17:32
ReporteralostaleView Statuspublic 
Assigned Toalostale 
PriorityimmediateResolutionfixedFixed in Version3.0PR16Q1
StatusclosedFix in branchFixed in SCM revisionc984f59ed409
ProjectionnoneETAnoneTarget Version3.0PR16Q1
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Tocaristu
Web browser
ModulesCore
Regression levelProduction - QA Approved
Regression date2015-07-03
Regression introduced in release3.0PR15Q4
Regression introduced by commithttps://code.openbravo.com/erp/devel/pi/rev/b26a24d2053e04743e90c430dc6f14098348651b [^]
Triggers an Emergency PackNo
Summary

0032309: error on update if entity persistence observer loaded current object in memory

DescriptionIf an entity persistence observer loas current object in memory, an error is thrown when trying to perform an update from UI.
Steps To Reproduce-Add to attached OrderLineObserver.java to sources and compile
-Try to edit any existent order line.
  -> The following error can be seen:
    Saving failed. a different object with the same identifier value was already associated with the session: [OrderLine#7517250EF33F451CAF1CFF9A1CA5FEC9]
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks defect 0032308 closedalostale error on update if entity persistence observer loaded current object in memory 

-  Notes
(0084465)
hgbot (developer)
2016-02-24 15:24

Repository: erp/backports/3.0PR16Q1
Changeset: c984f59ed409c5be65ebefb64d28fa1ac4b641a6
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Tue Feb 23 16:37:30 2016 +0100
URL: http://code.openbravo.com/erp/backports/3.0PR16Q1/rev/c984f59ed409c5be65ebefb64d28fa1ac4b641a6 [^]

fixed bug 32309: error on update if an observer loaded current object in memory

  In case an entity observer loaded current object in memory (ie. observing orderLine)
  doing orderLine.getSalesOrder().getOrderLineList() there were two different instances
  in memory representing the same DB row. This caused problems when trying to evict it.
  Causing an exception to be thrown when updating from UI in this case.

  As solution eviction is no longer performed, object is forced to be fetched from DB by
  executing a Criteria.

---
M modules/org.openbravo.service.json/src/org/openbravo/service/json/DefaultJsonDataService.java
---
(0084472)
caristu (developer)
2016-02-24 17:32

Code review + testing OK

- Issue History
Date Modified Username Field Change
2016-02-23 10:58 alostale Type defect => backport
2016-02-23 10:58 alostale Target Version => 3.0PR16Q1
2016-02-24 15:05 alostale Review Assigned To => caristu
2016-02-24 15:24 hgbot Checkin
2016-02-24 15:24 hgbot Note Added: 0084465
2016-02-24 15:25 hgbot Status scheduled => resolved
2016-02-24 15:25 hgbot Resolution open => fixed
2016-02-24 15:25 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/backports/3.0PR16Q1/rev/c984f59ed409c5be65ebefb64d28fa1ac4b641a6 [^]
2016-02-24 17:32 caristu Note Added: 0084472
2016-02-24 17:32 caristu Status resolved => closed
2016-02-24 17:32 caristu Fixed in Version => 3.0PR16Q1


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker