Endless requests breaking sites #2365
Comments
Note the additional comment suggesting this was related to having PHP 5.6 & updating to 7.X fixed it. |
I did note that and I added that information to Wordpress.org too. However,
that did not fix the issue for me. I downgraded to the prior version of
Woocommerce and that "fixed it". That wasn't really a "fix", so let me
change that and say that I got my account up and running again by
downgrading.
…On Wed, Jun 5, 2019 at 9:08 PM Ron Rennick ***@***.***> wrote:
Note the additional comment suggesting this was related to having PHP 5.6
& updating to 7.X fixed it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2365?email_source=notifications&email_token=AL4BLG4ROJUYP4PPRP4POUDPZBPQHA5CNFSM4HT6SZK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXBOC4I#issuecomment-499310961>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AL4BLG56REBFUPM6XSJACKLPZBPQHANCNFSM4HT6SZKQ>
.
|
I have been attempting to recreate this issue locally - so specifically seeing if I can recreate a problem where on legacy Woo pages ( i.e. Orders, Products, Product Edit ). The pattern of the API requests shown in the OP here align with the requests generated from the Activity Panels. Here is a screen grab of my network tab when loading a product listing page: Doing standard operations like editing products I could not recreate the flood of requests noted by a few users in the forums. So I decided to make some of the endpoints fail on purpose using So with this simulated REST API crashing in place, fresh-data continues to retry the requests every 2 seconds, which results in: ... and the fans on my laptop going crazy. So if this is indeed what is happening - all REST API requests failing on a legacy page for whatever reason, the above scenario will be x4, which would be quite a few requests being issued to an already languishing server. Additionally it appears that our implementation to reduce the freshness interval ( #1549 ) is not being respected anymore, as the retries are happening every 2 seconds. And @jeffstieler's fix to not dispatch REST API requests via fresh-data when a window is not active in the browser is not preventing the requests from firing ( #1732 ). So if a site's REST API server is down, and a tab is even running in the background, things could very likely escalate to what is being reported here. I propose we do the following - likely spawning off some new issues for each:
|
Hmm, this is pretty strange behavior. I'll set up a test environment to check this out too. |
Another report: 2092809-zen |
I've been trying this out locally on a vvv build and I've not been able to make this happen. If I insert a 20 seconds is interesting, since it's not what's being set, from what I can tell, but it is the default for fresh-data. Not sure where the timeout requirement isn't being set to make it go to default. But anyway, is there some other trigger I can try to make this happen? BTW, this is on current master for both Update: I've even tried the following to simulate a 403 situation and still it only goes every 20 seconds.
|
I managed to make this happen by switching tabs after the timeout starts occurring. This results in a rapid requesting of the timed out resource. I've created a fix in #2387 |
@BodyStatements to which version did you revert? |
This is a copy of an issue logged in WooCommerce, woocommerce/woocommerce#23868.
cc @BodyStatements
The text was updated successfully, but these errors were encountered: