Openbravo Issue Tracking System - Retail Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0038895Retail ModulesWeb POSpublic2018-05-24 12:592018-07-05 10:47
Reporterjorge-garcia 
Assigned Tojorge-garcia 
PriorityurgentSeveritymajorReproducibilitysometimes
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionRR18Q2.1Fixed in VersionRR18Q2.1 
Merge Request Status
Review Assigned Toguilleaer
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0038895: 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.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
blocks defect 0038615 closed jorge-garcia For each masterdata records insert failure webPOS generates a new masterdata request thread 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2018-07-05 08:29jorge-garciaTypedefect => backport
2018-07-05 08:29jorge-garciaTarget Version => RR18Q2.1
2018-07-05 10:26hgbotCheckin
2018-07-05 10:26hgbotNote Added: 0105623
2018-07-05 10:26hgbotStatusscheduled => resolved
2018-07-05 10:26hgbotResolutionopen => fixed
2018-07-05 10:26hgbotFixed in SCM revisionhttp://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:47guilleaerReview Assigned Tomarvintm => guilleaer
2018-07-05 10:47guilleaerStatusresolved => closed
2018-07-05 10:47guilleaerFixed in Version => RR18Q2.1
2019-12-30 17:33AtulOpenbravoRelationship addedcauses 0042506
2019-12-30 17:33AtulOpenbravoRelationship deletedcauses 0042506

Notes
(0105623)
hgbot   
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
---