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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0036323
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] StoreServermajorhave not tried2017-06-23 12:152017-10-02 10:20
ReportermtaalView Statuspublic 
Assigned Tomtaal 
PrioritynormalResolutionduplicateFixed 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

0036323: When the server is processing a message still then do not execute success or failure on the client

DescriptionWhen the server is retrying its message (see related issue) and it is still being processed on the server then do not execute the success/error callback on the client. By not doing calling these callbacks the processing popup remains visible.
Steps To ReproduceRun synchronized mode
Put a breakpoint in the OrderLoader
The webpos message layer will retry the message
Check that in the MultiServerJSONProcess it will find that the message is already being processed and a success message is returned.
This success message will cause the popup from going away.
Proposed SolutionReturn a flag in the message and handle it in the ob-request-router, so that the popup is not closed
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
duplicate of defect 0036790 closedmigueldejuana Synchronized mode has problems when the request to the backend reaches timeout 
related to feature request 0036536RR17Q4 closedmtaal Store response for external order loader and resend if duplicate message is received 
related to feature request 0036538 closedmtaal MultiServerJSONProcess: When a message from the webpos is duplicated send the original response 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2017-06-23 12:15 mtaal New Issue
2017-06-23 12:15 mtaal Assigned To => mtaal
2017-06-23 12:15 mtaal Triggers an Emergency Pack => No
2017-07-27 10:13 mtaal Relationship added related to 0036536
2017-07-27 10:19 mtaal Relationship added related to 0036538
2017-10-02 10:20 mtaal Relationship added duplicate of 0036790
2017-10-02 10:20 mtaal Status new => closed
2017-10-02 10:20 mtaal Resolution open => duplicate

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker