Project:
| View Revisions: Issue #34440 | [ Back to Issue ] | ||
| Summary | 0034440: [RR16Q4][HighVol] Click several times in Layaways search button and/or in SEARCH search button creates heavy postgres processes | ||
| Revision | 2016-11-09 10:33 by lorenzofidalgo | ||
| Steps To Reproduce | 0-Log in to the server machine and use "top" command to control the CPU usage of the server machine. 1-Go to SEARCH tab and click several times (e.g. 6 times) in Search button. Now go to dropdown menu, select Layaways option and click several times (e.g. 6 times) in search button. It will get stuck. You can go again to SEARCH tab and click again in search button. Check it is stuck and no results are shown. 3-Check the usage of the server machine (step 0): Many postgres processes that will not finish have been created. Even after login out those processes are still there. You can eve wait some time after executing this queries and check those postgres processes are still running. |
||
| Revision | 2016-11-09 10:33 by lorenzofidalgo | ||
| Description | When POS user clicks in the magnifier button (search) from areas like SEARCH or Layaways, it creates several heavy processes that take very long time to finish (or they just do not finish). It induces the POS gets stuck. This issue has been reproduced in a RR16Q4 release with Store Server and HighVol. This behaviour can been appreciated in the following video: https://drive.google.com/open?id=0Bz1bUfkEffVISURjYm5DbEV6NkU [^] |
||
| Revision | 2016-11-09 10:01 by lorenzofidalgo | ||
| Steps To Reproduce | 0-Log in to the server machine and use "top" command to control the CPU usage of the server machine. 1-Go to BROWSE tab and click several times (e.g. 6 times) in Search button. Now go to dropdown menu, select Layaways option and click several times (e.g. 6 times) in search button. It will get stuck. You can go again to BROWSE tab and click again in search button. Check it is stuck and no results are shown. 3-Check the usage of the server machine (step 0): Many postgres processes that will not finish have been created. Even after login out those processes are still there. You can eve wait some time after executing this queries and check those postgres processes are still running. |
||
| Revision | 2016-11-09 09:53 by lorenzofidalgo | ||
| Description | When POS user clicks in the magnifier button (search) from areas like BROWSE or Layaways, it creates several heavy processes that take very long time to finish (or they just do not finish). It induces the POS gets stuck. This issue has been reproduced in a RR16Q4 release with Store Server and HighVol. This behaviour can been appreciated in the following video: https://drive.google.com/open?id=0Bz1bUfkEffVISURjYm5DbEV6NkU [^] |
||
| Revision | 2016-11-09 09:50 by lorenzofidalgo | ||
| Description | When POS user clicks in the magnifier button (search) from areas like BROWSE or Layaways, it creates several heavy processes that take very long time to finish (or they just do not finish). It induces the POS gets stuck. | ||
| Copyright © 2000 - 2009 MantisBT Group |
 |