Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
backport[Retail Modules] Web POSmajoralways2018-02-12 12:182018-02-13 19:01
ReportermigueldejuanaView Statuspublic 
Assigned ToRetail 
PrioritynormalResolutionfixedFixed in VersionRR18Q1
StatusclosedFix in branchFixed in SCM revision4946a644c779
ProjectionnoneETAnoneTarget VersionRR18Q1
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Tomarvintm
Regression levelProduction - Confirmed Stable
Regression date2017-10-27
Regression introduced in releaseRR17Q4
Regression introduced by commit [^]
Triggers an Emergency PackNo

0037902: When Incremental fails POS gets unestable.

DescriptionWhen an incremental refresh fails in the login process the POS gets unstable.
Steps To Reproduce- Login in Web POS
. Create and order, paid it fully and press SCAN button
- Add a breakpoint in
- Press F5 and you will see the breakpoint stopping the execution
- POS moves to offline and the resume the execution(F8 in Eclipse)
- ERROR! BP and BPL is empty, then is set, then empty again
- ERROR! Document Number empty, then is set, then empty again
- ERROR! Total is 0, then is set to the real total, then empty again
- ERROR! If we go to payment panel, Done button is not there or if it is there, pressing it makes POS to fail.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks defect 0037884 closedmigueldejuana When Incremental fails POS gets unestable. 

-  Notes
hgbot (developer)
2018-02-13 15:49

Repository: retail/backports/3.0RR18Q1/
Changeset: 7b6c7666decf535c56af0b90ab186892dc2e29c2
Author: Miguel de Juana <miguel.dejuana <at>>
Date: Tue Feb 13 15:49:38 2018 +0100
URL: [^]

Fixed issue 0037902: When Incremental fails POS gets unestable.

- We must stop the incremental refresh if one model fails because we don't need to retrieve data because we have enough data to work. Doing a full refresh we need to continue retrieving models to charge them and failed models will be charged in the next try of login.

M web/
hgbot (developer)
2018-02-13 16:59

Repository: retail/backports/3.0RR18Q1/
Changeset: 4946a644c7791eb2fe02359b3279c17967400099
Author: Antonio Moreno <antonio.moreno <at>>
Date: Tue Feb 13 16:59:23 2018 +0100
URL: [^]

Fixed issue 37902. Case when the backend returns error will now be handled correctly on incremental.

M web/

- Issue History
Date Modified Username Field Change
2018-02-13 13:24 migueldejuana Type defect => backport
2018-02-13 13:24 migueldejuana Target Version => RR18Q1
2018-02-13 15:49 hgbot Checkin
2018-02-13 15:49 hgbot Note Added: 0102370
2018-02-13 15:49 hgbot Status scheduled => resolved
2018-02-13 15:49 hgbot Resolution open => fixed
2018-02-13 15:49 hgbot Fixed in SCM revision => [^]
2018-02-13 16:59 hgbot Checkin
2018-02-13 16:59 hgbot Note Added: 0102376
2018-02-13 16:59 hgbot Fixed in SCM revision [^] => [^]
2018-02-13 19:01 marvintm Review Assigned To => marvintm
2018-02-13 19:01 marvintm Status resolved => closed
2018-02-13 19:01 marvintm Fixed in Version => RR18Q1

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker