Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0040297Openbravo ERPA. Platformpublic2019-02-21 13:292019-03-08 10:48
caristu 
jarmendariz 
immediateminorhave not tried
closedfixed 
5
 
3.0PR18Q3.6 
caristu
Core
Production - Confirmed Stable
2018-02-18
3.0PR18Q2
https://code.openbravo.com/erp/devel/pi/rev/0b908a2c7f992827a230b06193ad7f8f9bd2ce9b [^]
No
0040297: Responses from OB.RemoteCallManager calls are not handled if the Smartclient timeout is fired
Responses from OB.RemoteCallManager calls are not handled if the Smartclient timeout is fired . This is a change in the behavior introduced with the following changeset[1].

Before that change the timeout error was not being properly handled causing the thrown of JS errors in the console. Despite this errors, the response was being handled by Smatclient.

Now the timeout error is being handled, showing the message in the UI. But seems that this causes the request response to be ignored when it finishes.

[1] https://code.openbravo.com/erp/devel/pi/rev/0b908a2c7f992827a230b06193ad7f8f9bd2ce9b#l1.37 [^]
Artificial test:

1) Open the [Sales Order] window
2) Create a new sales order with at least one line and book it
3) Open the Add Payment window
4) Using the dev tools console reduce the timeout to be able to simulate the timeout expiration: isc.RPCManager.defaultTimeout = 1000
5) Put a breakpoint in the AddPaymentActionHandler class
6) In the client the message information about the timeout expiration appears
7) Step over the breakpoint and finish the execution of the handler --> note that the response message from the action handler does not apper

Before the mentioned changeset, the behavior was different:

1) The timeout message was not appearing (the error was thrown in the console instead)
2) The process pop-up was closed
3) The message from the action handler was shown properly in the header
No tags attached.
blocks defect 0040253 closed jarmendariz Responses from OB.RemoteCallManager calls are not handled if the Smartclient timeout is fired 
Issue History
2019-02-28 17:10jarmendarizTypedefect => backport
2019-02-28 17:10jarmendarizTarget Version => 3.0PR18Q3.6
2019-02-28 18:50hgbotCheckin
2019-02-28 18:50hgbotNote Added: 0110134
2019-02-28 18:50hgbotStatusscheduled => resolved
2019-02-28 18:50hgbotResolutionopen => fixed
2019-02-28 18:50hgbotFixed in SCM revision => http://code.openbravo.com/erp/backports/3.0PR18Q3.6/rev/4204737440a31da3fe46d658da2639541072c354 [^]
2019-03-08 10:48caristuReview Assigned To => caristu
2019-03-08 10:48caristuNote Added: 0110310
2019-03-08 10:48caristuStatusresolved => closed

Notes
(0110134)
hgbot   
2019-02-28 18:50   
Repository: erp/backports/3.0PR18Q3.6
Changeset: 4204737440a31da3fe46d658da2639541072c354
Author: Javier Armendáriz <javier.armendariz <at> openbravo.com>
Date: Thu Feb 28 10:53:54 2019 +0100
URL: http://code.openbravo.com/erp/backports/3.0PR18Q3.6/rev/4204737440a31da3fe46d658da2639541072c354 [^]

Fixed issue 40297: RemoteCallManager response not handled when timemout is fired.

Removed result sanitizing in RPCManager. This makes timeout message appears but
also marks the request as complete and the actual response is not processed when
it arrives.

---
M modules/org.openbravo.userinterface.smartclient/web/org.openbravo.userinterface.smartclient/js/ob-smartclient.js
---
(0110310)
caristu   
2019-03-08 10:48   
Code reviewed + tested OK.