Project:
| View Revisions: Issue #41686 | [ All Revisions ] [ Back to Issue ] | ||
| Summary | 0041686: Polling when creating a subscription with card number does not always return data from the server | ||
| Revision | 2019-08-23 14:34 by markmm82 | ||
| Description | Sometimes after creating several subscriptions consecutively, the polling is failing and the response does not return from the server. This means that the data on the client is not updated correctly with the information generated on the server during the subscription processing (memberID, category, points earned by the subscription, etc.) and sometimes causes the user interfaces that remain waiting to show the updated data. After the timeout passes, an error is shown in the browser log showing that the process of saving the subscription failed by the timeout. When this happens, sometimes in the next subscription, the polling response brings the previous information (which failed) and the current subscription. Specifically, this issue can be reproduced when the Card Number field is set in the subscription. After many iterations without defining this field at the time of creating the subscription (manual or automatic at the time of customers creation) could not be reproduced. Right now this issue is making to fail some tests of the Loyalty Programs suite. Attached you will find linf for two videos when this issue is reproduced randomly after some tries. It is needed sometimes more than 10 attempts to reproduce it. At try it is failing much more faster. [1] https://drive.google.com/open?id=1d3WtinFy0NBK5kfQMCRSUzz1zPLev6Zd [^] [2] https://drive.google.com/open?id=1m6p22yJZ1kRYY2kM03GWy0Eo8z1S6JAU [^] |
||
| Revision | 2019-08-23 14:31 by markmm82 | ||
| Description | Sometimes after creating several subscriptions consecutively, the polling is failing and the response does not return from the server. This means that the data on the client is not updated correctly with the information generated on the server during the subscription processing (memberID, category, points earned by the subscription, etc.) and sometimes causes the user interfaces that remain waiting to show the updated data. After the timeout passes, an error is shown in the browser log showing that the process of saving the subscription failed by the timeout. When this happens, sometimes in the next subscription, the polling response brings the previous information (which failed) and the current subscription. Specifically, this issue can be reproduced when the Card Number field is set in the subscription. After many iterations without defining this field at the time of creating the subscription (manual or automatic at the time of customers creation) could not be reproduced. Right now this issue is making to fail some tests of the Loyalty Programs suite. Attached you will find two videos when this issue is reproduced randomly after some tries. It is needed sometimes more than 10 attempts to reproduce it. At try it is failing much more faster. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |