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 VersionRR17Q4.1
StatusclosedFix in branchFixed in SCM revisionc80895e3f445
ProjectionnoneETAnoneTarget VersionRR17Q4.1
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

0037903: 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
migueldejuana (developer)
2018-02-13 15:49

Repository: retail/backports/3.0RR17Q4.1/
Changeset: 69e8795b9a78d3aa996f5f1e62be9c8f5a46d744
Author: Miguel de Juana <miguel.dejuana <at>>
Date: Tue Feb 13 15:47:36 2018 +0100
URL: [^] [^]

Fixed issue 0037884: 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 17:02

Repository: retail/backports/3.0RR17Q4.1/
Changeset: c80895e3f445bbb8950d5a74a7d0607f5e73b9f6
Author: Miguel de Juana <miguel.dejuana <at>>
Date: Tue Feb 13 17:02:18 2018 +0100
URL: [^]

Fixed issue 0037903: When Incremental fails POS gets unestable.

- 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 => RR17Q4.1
2018-02-13 15:49 migueldejuana Note Added: 0102369
2018-02-13 15:49 migueldejuana Status scheduled => resolved
2018-02-13 15:49 migueldejuana Resolution open => fixed
2018-02-13 17:02 hgbot Checkin
2018-02-13 17:02 hgbot Note Added: 0102377
2018-02-13 17:02 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 => RR17Q4.1

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker