Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0037250 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
defect | [Retail Modules] StoreServer | minor | have not tried | 2017-11-07 13:41 | 2018-06-08 16:26 | |||
Reporter | mtaal | View Status | public | |||||
Assigned To | mtaal | |||||||
Priority | normal | Resolution | unable to reproduce | Fixed in Version | ||||
Status | closed | Fix in branch | Fixed in SCM revision | |||||
Projection | none | ETA | none | Target Version | ||||
OS | Any | Database | Any | Java version | ||||
OS Version | Database version | Ant version | ||||||
Product Version | SCM revision | |||||||
Review Assigned To | ||||||||
Regression level | ||||||||
Regression date | ||||||||
Regression introduced in release | ||||||||
Regression introduced by commit | ||||||||
Triggers an Emergency Pack | No | |||||||
Summary | 0037250: CS down during ticket processing makes WP/SS to go offline but ticket is removed from UI | |||||||
Description | When the SS goes offline during ticket processing then the ticket is removed from the UI. This is not correct. This happens when the central server goes down during ticket processing. The following exception is thrown then: java.net.ConnectException: Connection refused. This is thrown on the store server which waits for central server processing. The store server will retry to send the request but it fails and it will transition to offline. The user is forced to logoff (as transition to offline happens). The created import entry archive is set to processed, this because the only thing which is detected is that the central server goes offline. The user is logged off, after going offline and logging in again the ticket is not present anymore in webpos. Probably because the case is not seen as an error. | |||||||
Steps To Reproduce | Install multi-server Put a breakpoint in the CS orderloader Submit ticket from webpos, system stops in CS orderloader Stop CS This is detected by SS and WP --> go offline The user is forced to logoff When the user can later login the ticket is not there anymore | |||||||
Proposed Solution | In case of a TOF reaction execute the error callback and not the success callback in the ob-requestrouter.js file. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | ||||||||
|
Notes | |
(0105045) mtaal (manager) 2018-06-08 16:26 |
Does not happen anymore in latest version of the code |
Issue History | |||
Date Modified | Username | Field | Change |
2017-11-07 13:41 | mtaal | New Issue | |
2017-11-07 13:41 | mtaal | Assigned To | => StoreServer |
2017-11-07 13:41 | mtaal | Triggers an Emergency Pack | => No |
2017-11-23 10:42 | mtaal | Assigned To | StoreServer => mtaal |
2017-12-01 10:02 | mtaal | Relationship added | has duplicate 0037254 |
2018-06-08 16:26 | mtaal | Note Added: 0105045 | |
2018-06-08 16:26 | mtaal | Status | new => closed |
2018-06-08 16:26 | mtaal | Resolution | open => unable to reproduce |
Copyright © 2000 - 2009 MantisBT Group |