Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0040342
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Openbravo ERP] A. Platformminorhave not tried2019-03-08 11:052022-02-01 08:07
ReportercaristuView Statuspublic 
Assigned ToTriage Platform Base 
PriorityhighResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0040342: Define a default query timeout profile for the standard grids

DescriptionA default query timeout profile should be defined for the standard grids. Currently there is a timeout in Smartclient[1] that defines, among others, how long the requests fired by the standard grids should last before returning an error.

Currently, when this timeout is reached, an error message is properly shown in the grid and the grid data will not be updated, but this does not affect to the request (query) execution in the backend which is not being cancelled.


[1] https://www.smartclient.com/smartclient-release/isomorphic/system/reference/?id=search%3DdefaultTimeout [^]
Steps To ReproduceIn description
Proposed SolutionDefine a default db.queryTimeout.grid in Openbravo properties.template. Its value should be a bit less than the value of RPCManager.defaultTimeout.
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
related to defect 0040253 closedjarmendariz Responses from OB.RemoteCallManager calls are not handled if the Smartclient timeout is fired 
related to defect 0035268 closedjarmendariz Request timeout message is not handled properly in the UI 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2019-03-08 11:05 caristu New Issue
2019-03-08 11:05 caristu Assigned To => platform
2019-03-08 11:05 caristu Modules => Core
2019-03-08 11:05 caristu Triggers an Emergency Pack => No
2019-03-08 11:05 caristu Issue generated from 0040253
2019-03-08 11:05 caristu Relationship added related to 0040253
2019-03-08 11:07 caristu Description Updated View Revisions
2019-03-08 11:07 caristu Relationship added related to 0035268
2019-03-26 09:01 alostale Status new => acknowledged
2019-03-26 09:01 alostale Type defect => feature request
2019-05-06 08:25 alostale Target Version => 3.0PR19Q3
2019-05-06 09:12 caristu Proposed Solution updated
2019-06-20 09:20 caristu Target Version 3.0PR19Q3 => 3.0PR19Q4
2019-12-04 12:30 alostale Target Version 3.0PR19Q4 =>
2022-02-01 08:07 alostale Assigned To platform => Triage Platform Base

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker