Openbravo Issue Tracking System - Retail Modules |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0054811 | Retail Modules | Web POS Hardware Manager | public | 2024-02-29 17:39 | 2024-04-10 16:22 |
|
| Reporter | malsasua | |
| Assigned To | ignacio_deandres | |
| Priority | high | Severity | major | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
| Merge Request Status | |
| Review Assigned To | adrianromero |
| OBNetwork customer | |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0054811: Sometimes, the winpay WS session is lost and it is not managed properly |
| Description | In one customer, sometimes, we have a log trace in HW Manager informing the WS session was closed, and the POS is locked waiting the response.
The message in hw manager log is:
WARNING: WebSoccket Session already closed. Message Lost. |
| Steps To Reproduce | 00:00:00 -> customer starts HW Manager
00:01:00 -> WYNPAY_LOGIN request is sent
00:01:01 -> message WARNING: WebSocket Session already closed. Message Lost.
00:01:30 -> WINPAY MAINTENANCE request is sent
00:01:31 -> message WARNING: WebSocket Session already closed. Message Lost. |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | defect | 0054862 | | closed | ignacio_deandres | Wynpay: error when resultCode is empty |
|
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2024-02-29 17:39 | malsasua | New Issue | |
| 2024-02-29 17:39 | malsasua | Assigned To | => Triage Platform Conn |
| 2024-02-29 17:39 | malsasua | Triggers an Emergency Pack | => No |
| 2024-03-01 13:48 | adrianromero | Assigned To | Triage Platform Conn => ignacio_deandres |
| 2024-03-06 13:42 | malsasua | Relationship added | related to 0054862 |
| 2024-04-03 13:23 | adrianromero | Note Added: 0162812 | |
| 2024-04-03 13:28 | adrianromero | Note Added: 0162813 | |
| 2024-04-08 08:51 | adrianromero | Note Added: 0162905 | |
| 2024-04-10 15:40 | adrianromero | Status | new => acknowledged |
| 2024-04-10 16:21 | adrianromero | Status | acknowledged => scheduled |
| 2024-04-10 16:21 | adrianromero | Status | scheduled => resolved |
| 2024-04-10 16:21 | adrianromero | Resolution | open => fixed |
| 2024-04-10 16:22 | adrianromero | Review Assigned To | => adrianromero |
| 2024-04-10 16:22 | adrianromero | Note Added: 0163062 | |
| 2024-04-10 16:22 | adrianromero | Status | resolved => closed |
|
Notes |
|
|
|
|
Need to check whether using the new Jetty 10 libraries this error is still reproducible |
|
|
|
|
New Hardware Manager with the new Jetty 10 libraries have been validated and no errors have been reported up until now.
Waiting for the end of the week to close the issue if no errors are reported. 5/4/2024 |
|
|
|
|
Waiting for customer answer whether the issue is still reproducible or not
|
|
|
|
|
|
No incidences after the update of Jetty libraries. Closing issue. |
|