Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] StoreServermajorhave not tried2018-05-07 15:402018-05-10 17:13
ReporterAugustoMauchView Statuspublic 
Assigned ToStoreServer 
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

0038497: If the store server receives a response from the central server with bad JSON format, it should not go offline

DescriptionThe MobileServerRequestExecutor.executeServerRequest method executes a request in a remote server. For instance, it is used to forward a request from the store server to the central server.

If the central server is not available or cannot process the request, the store server will transition to offline.

This behavior is too strict, the store server should only transition to offline is the central server is not available, but not if it returns a response and there is a problem with the response itself (i.e. it is badly formatted).
Steps To ReproduceIn a production environment, there was a problem when process a request in the central server, and the store server received a badly formatted JSON response (see [1]). In this case the store server should have not transitioned to offline, because the central server was available.

[1] [^]
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
duplicate of design defect 0038505 closedAugustoMauch Before going offline do extra ping request 
related to defect 0038496 scheduledrqueralta Exception in ProcessHQLQuery can result in error JSON response being not properly formatted 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2018-05-07 15:40 AugustoMauch New Issue
2018-05-07 15:40 AugustoMauch Assigned To => StoreServer
2018-05-07 15:40 AugustoMauch Triggers an Emergency Pack => No
2018-05-07 15:40 AugustoMauch Relationship added related to 0038496
2018-05-07 15:42 AugustoMauch Steps to Reproduce Updated View Revisions
2018-05-10 17:13 AugustoMauch Relationship added duplicate of 0038505
2018-05-10 17:13 AugustoMauch Status new => closed
2018-05-10 17:13 AugustoMauch Resolution open => duplicate

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker