Openbravo Issue Tracking System - POS2
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0054404POS2POSpublic2024-01-19 18:422024-03-19 13:07
Reportercharlotte_vasseur 
Assigned ToTriage Platform Base 
PrioritynormalSeveritymajorReproducibilityrandom
StatusclosedResolutioninvalid 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Tocberner
OBNetwork customer
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0054404: [OFFLINE] Sometimes POS fails to reconnect after the counter
DescriptionWhen offline, after going back online sometimes POS succeeds to reconnect (See "Reconnect POS OK.mkv")
And sometimes it fails (See "Reconnect POS KO.mkv")
Steps To ReproduceWhile online
Log in POS
Go offline
The counter 30s starts
Go back online
Wait that the counter reaches 0
=> Sometimes POS fails to reconnect
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files? Reconnect POS OK.mkv (1,940,386) 2024-01-19 18:42
https://issues.openbravo.com/file_download.php?file_id=19356&type=bug
? Reconnect POS KO.mkv (1,932,264) 2024-01-19 18:42
https://issues.openbravo.com/file_download.php?file_id=19357&type=bug
Issue History
Date ModifiedUsernameFieldChange
2024-01-19 18:42charlotte_vasseurNew Issue
2024-01-19 18:42charlotte_vasseurAssigned To => Retail
2024-01-19 18:42charlotte_vasseurFile Added: Reconnect POS OK.mkv
2024-01-19 18:42charlotte_vasseurTriggers an Emergency Pack => No
2024-01-19 18:42charlotte_vasseurFile Added: Reconnect POS KO.mkv
2024-01-20 11:29rafarodaSeverityminor => major
2024-02-28 08:56sreehariAssigned ToRetail => sreehari
2024-02-28 12:40sreehariStatusnew => scheduled
2024-03-05 11:55sreehariNote Added: 0161662
2024-03-06 11:23guillermogilAssigned Tosreehari => Triage Platform Base
2024-03-06 11:50guillermogilStatusscheduled => resolved
2024-03-06 11:50guillermogilResolutionopen => fixed
2024-03-06 11:50guillermogilStatusresolved => new
2024-03-06 11:50guillermogilResolutionfixed => open
2024-03-19 10:22cbernerNote Added: 0162333
2024-03-19 10:22cbernerNote Edited: 0162333bug_revision_view_page.php?bugnote_id=0162333#r27710
2024-03-19 10:22cbernerNote Edited: 0162333bug_revision_view_page.php?bugnote_id=0162333#r27711
2024-03-19 10:59cbernerStatusnew => feedback
2024-03-19 12:39charlotte_vasseurNote Added: 0162363
2024-03-19 13:07cbernerReview Assigned To => cberner
2024-03-19 13:07cbernerNote Added: 0162364
2024-03-19 13:07cbernerStatusfeedback => closed
2024-03-19 13:07cbernerResolutionopen => invalid

Notes
(0161662)
sreehari   
2024-03-05 11:55   
Steps to reproduce:
*******************
1.Keep a breakpoint in https://gitlab.com/openbravo/devel/pmods/org.openbravo.mobile.core/-/blob/master/web/org.openbravo.mobile.core/app/integration/remote-server/BackendServer.js?ref_type=heads#L550 [^]
2.keep the network tab in offline in devtools
3.Make the pos go offline by browsing the orders list
4.when 30sec countdown starts, breakpoint will stop every 10 secs, for 1 ping skip the breakpoint, before the second ping turn network tab to no throttling
5.Now even though we have isAvailable = true, we are not connected back due to this failing case this.requestValidationCounter === 0 &&
(0162333)
cberner   
2024-03-19 10:22   
This is intended behavior, the network is checked for instability, basically during the 30 second countdown after going offline, we launch a request each 1/3 of the max time(10 seconds), if any of these requests fail, we consider the network as unstable and keep in offline mode.

Only when all 3 requests are successful the network is considered stable enough and we do the switch to online. The switch to online can always be manually forced, by clicking on the "try now" button on the timer dialog.
(0162363)
charlotte_vasseur   
2024-03-19 12:39   
Hi, as confirmed with Rafa Roda, we are okay with this explanation
Thanks !
(0162364)
cberner   
2024-03-19 13:07   
This is intended behavior, so I'm rejecting this issue.