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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0038895
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Retail Modules] Web POSmajorsometimes2018-05-24 12:592018-07-05 10:47
Reporterjorge-garciaView Statuspublic 
Assigned Tojorge-garcia 
PriorityurgentResolutionfixedFixed in VersionRR18Q2.1
StatusclosedFix in branchFixed in SCM revisionac6d53eb3c63
ProjectionnoneETAnoneTarget VersionRR18Q2.1
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Toguilleaer
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0038895: For each masterdata records insert failure webPOS generates a new masterdata request thread

DescriptionFor each masterdata records insert failure webPOS generates a new masterdata request thread
Steps To Reproduce1) Clear the cache to force a full refresh
2) Load webPOS page
3) Put a breakpoint in tx.executeSql(insertStatement, values, null, handleError);
4) Login webPOS
5) Ignore breakpoint until masterdata models starts to be executed (i.e. Product)
6) Using console, change insertStatement variable to ""
7) Deactivate the breakpoint and continue the process. Infinite request are done to masterdata Category.
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
blocks defect 0038615 closedjorge-garcia For each masterdata records insert failure webPOS generates a new masterdata request thread 

-  Notes
(0105623)
hgbot (developer)
2018-07-05 10:26

 Repository: retail/backports/3.0RR18Q2.1/org.openbravo.mobile.core
Changeset: ac6d53eb3c6354c5cbb9a2d5bd6afe4a0aadf6ff
Author: Jorge Garcia <jorge.garcia <at> openbravo.com>
Date: Thu Jul 05 08:52:03 2018 +0200
URL: http://code.openbravo.com/retail/backports/3.0RR18Q2.1/org.openbravo.mobile.core/rev/ac6d53eb3c6354c5cbb9a2d5bd6afe4a0aadf6ff [^]

Fixed issue 38895: For each masterdata records insert failure webPOS
generates a new masterdata request thread

If insert or update transaction fail, the error callback should not execute the
next model. Instead of that, it should generate a error log message and make
the transaction to fail.

To indicate the transaction has failed, it is necessary to return true in error
callback in transaction sql.

Include error and warning log message to logclient and console, instead of
show it only on console.

Include transaction error in message.

---
M web/org.openbravo.mobile.core/source/data/ob-dal.js
M web/org.openbravo.mobile.core/source/data/ob-datasource.js
---

- Issue History
Date Modified Username Field Change
2018-07-05 08:29 jorge-garcia Type defect => backport
2018-07-05 08:29 jorge-garcia Target Version => RR18Q2.1
2018-07-05 10:26 hgbot Checkin
2018-07-05 10:26 hgbot Note Added: 0105623
2018-07-05 10:26 hgbot Status scheduled => resolved
2018-07-05 10:26 hgbot Resolution open => fixed
2018-07-05 10:26 hgbot Fixed in SCM revision http://code.openbravo.com/erp/pmods/org.openbravo.mobile.core/rev/a5ef65a60fe69d039e4dcebbe353f0dfeae69a49 [^] => http://code.openbravo.com/retail/backports/3.0RR18Q2.1/org.openbravo.mobile.core/rev/ac6d53eb3c6354c5cbb9a2d5bd6afe4a0aadf6ff [^]
2018-07-05 10:47 guilleaer Review Assigned To marvintm => guilleaer
2018-07-05 10:47 guilleaer Status resolved => closed
2018-07-05 10:47 guilleaer Fixed in Version => RR18Q2.1
2019-12-30 17:33 AtulOpenbravo Relationship added causes 0042506
2019-12-30 17:33 AtulOpenbravo Relationship deleted causes 0042506

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker