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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0036538
TypeCategorySeverityReproducibilityDate SubmittedLast Update
feature request[Retail Modules] StoreServermajorhave not tried2017-07-27 10:182022-05-20 09:07
ReportermtaalView Statuspublic 
Assigned Tomtaal 
PrioritynormalResolutionopenFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0036538: MultiServerJSONProcess: When a message from the webpos is duplicated send the original response

DescriptionSee the related issue. The idea is to store the response. If the response is available then in the MultiServerJSONProcess [1] get this response and send it to the client.

Also if the message is being processed then wait a while for processing to be done. If processing is not done on time then return an error or show a message to the user with a choice. See related issue.
Steps To ReproduceSee related issue.
Proposed SolutionIn the code here [1] handle duplicate messages or messages already (being) processed by returning the response.

Also store the response.

Consider not using archive as this provides less visibility on errors.

[1]
https://code.openbravo.com/erp/pmods/org.openbravo.mobile.core/file/5b1201348091/src/org/openbravo/mobile/core/servercontroller/MultiServerJSONProcess.java#l146 [^]
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to feature request 0036536RR17Q4 closedmtaal Store response for external order loader and resend if duplicate message is received 
related to defect 0036323 closedmtaal When the server is processing a message still then do not execute success or failure on the client 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2017-07-27 10:18 mtaal New Issue
2017-07-27 10:18 mtaal Assigned To => mtaal
2017-07-27 10:18 mtaal Triggers an Emergency Pack => No
2017-07-27 10:19 mtaal Relationship added related to 0036536
2017-07-27 10:19 mtaal Relationship added related to 0036323
2017-12-28 09:57 mtaal Target Version RR17Q4 => RR18Q1
2018-02-14 12:59 mtaal Target Version RR18Q1 =>
2022-05-20 09:07 mtaal Status new => closed


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker