0034440: [RR16Q4][HighVol] Click several times in Layaways search button and/or in SEARCH search button creates heavy postgres processes

Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #34440		[ All Revisions ] [ 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: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.