Project:
| View Revisions: Issue #35268 | [ Back to Issue ] | ||
| Summary | 0035268: Request timeout message is not handled properly in the UI | ||
| Revision | 2017-02-24 10:30 by caristu | ||
| Description | The request timeout message is not being handled properly. If a request is not completed because the client timeout expires, then no message is displayed in the User Interface. Note that the only case where the message is displayed is when the timeout is expired when saving/updating a record in form view. This is because the ob-view detects that the response of the request is not successful. |
||
| Revision | 2017-02-15 08:51 by caristu | ||
| Steps To Reproduce | Artificial Test, using Eclipse: 1) Open any window, for example [Sales Order] 2) Put a breakpoint in the DefaultJsonDataService class, at the beginning of the fetch method. 3) Click on refresh button, wait 4 minutes without moving from the breakpoint. Once that time has passed, you will see in the UI that the "Loading data..." message in the header is gone but it does not appear any message informing about the timeout expiration. The same behavior happens when firing a call with OB.RemoteCallManager, but also in this case a js error is fired in the evalResult function because the timeout expiration result is not being handled properly: Uncaught TypeError: results.match is not a function at cons.evalResult (RPCManager.js:4291) at cons.fireReplyCallbacks (RPCManager.js:4308) at cons.performOperationReply (RPCManager.js:4265) at cons._performTransactionReply (RPCManager.js:4178) at cons.performTransactionReply (RPCManager.js:3595) at eval (eval at isc__makeFunction (Object.js:129), <anonymous>:3:16) at cons.fireCallback (Class.js:1789) at cons.performXmlTransactionReply (Comm.js:383) at eval (eval at isc__makeFunction (Object.js:129), <anonymous>:3:10) at Object.fireCallback (Class.js:1792) |
||
| Revision | 2017-02-15 08:41 by caristu | ||
| Steps To Reproduce | Artificial Test, using Eclipse: 1) Open any window, for example [Sales Order] 2) Put a breakpoint in the DefaultJsonDataService class, at the beginning of the fetch method. 3) Click on refresh button, wait 4 minutes without moving from the breakpoint. You will see that the "Loading data..." message in the header is gone but it does not appear any message informing about the timeout expiration. The same behavior happens when firing a call with OB.RemoteCallManager, but also in this case a js error is fired in the evalResult function because the timeout expiration result is not being handled properly: Uncaught TypeError: results.match is not a function at cons.evalResult (RPCManager.js:4291) at cons.fireReplyCallbacks (RPCManager.js:4308) at cons.performOperationReply (RPCManager.js:4265) at cons._performTransactionReply (RPCManager.js:4178) at cons.performTransactionReply (RPCManager.js:3595) at eval (eval at isc__makeFunction (Object.js:129), <anonymous>:3:16) at cons.fireCallback (Class.js:1789) at cons.performXmlTransactionReply (Comm.js:383) at eval (eval at isc__makeFunction (Object.js:129), <anonymous>:3:10) at Object.fireCallback (Class.js:1792) |
||
| Revision | 2017-02-15 08:37 by caristu | ||
| Steps To Reproduce | Artificial Test, using Eclipse: 1) Open any window, for example [Sales Order] 2) Put a breakpoint in the DefaultJsonDataService class, at the beginning of the fetch method. 3) Click on refresh button, wait 4 minutes without moving from the breakpoint. You will see that the "loading data..." message in the header is gone but it does not appear any message informing about the timeout expiration. The same behavior happens when firing a call with OB.RemoteCallManager, but also in this case a js error is fired in the evalResult function because the timeout expiration result is not being handled properly: Uncaught TypeError: results.match is not a function at cons.evalResult (RPCManager.js:4291) at cons.fireReplyCallbacks (RPCManager.js:4308) at cons.performOperationReply (RPCManager.js:4265) at cons._performTransactionReply (RPCManager.js:4178) at cons.performTransactionReply (RPCManager.js:3595) at eval (eval at isc__makeFunction (Object.js:129), <anonymous>:3:16) at cons.fireCallback (Class.js:1789) at cons.performXmlTransactionReply (Comm.js:383) at eval (eval at isc__makeFunction (Object.js:129), <anonymous>:3:10) at Object.fireCallback (Class.js:1792) |
||
| Revision | 2017-02-15 08:37 by caristu | ||
| Description | The request timeout message is not being handled properly. If a request is not completed because the client timeout expires, then no message is displayed in the User Interface. | ||
| Revision | 2017-02-15 08:37 by caristu | ||
| Description | The request timeout messages are not being handled properly. If a request is not completed because the client timeout expires, then no message is displayed in the UI. | ||
| Revision | 2017-02-14 19:34 by caristu | ||
| Description | The request timeout message is not being handled properly. If a request is not completed because the client timeout expires, then no message is displayed in the UI. | ||
| Copyright © 2000 - 2009 MantisBT Group |
 |