External tools limit exceed in Moodle 3.10

External tools limit exceed in Moodle 3.10

Jeewani Lakshani -
回帖数:8

Tools are not loading due to external tool limit is exceed from Moodle side. Therefore we need to increase the rate limit from Moodle. 

回复Jeewani Lakshani

Re: External tools limit exceed in Moodle 3.10

Jake Dallimore -
Core developers的头像 Moodle HQ的头像 Particularly helpful Moodlers的头像 Peer reviewers的头像 Plugin developers的头像 Testers的头像
Hi Jeewani,

I'm really not sure what you're referring to in this post. Can you please add a clear description of how you're setting up the LTI relationship and at what point you experience issues? If you see any errors, warnings etc, please include these too.

Thanks
Jake
回复Jake Dallimore

Re: External tools limit exceed in Moodle 3.10

Jeewani Lakshani -
We are in the process of creating LTI 1.3 external tools in Moodle3.10 instance. Once we create the tool, we need to access the tool and get information by clicking on the " View configuration details" icon.
The tools are not loading due to the time limit is exceeding. So, we cannot access the tools.
Below is the flow:
Moodle3.10 instance URL: http://3plcgmoodleprd.prd-prsn.com/moodle310/login/index.php
Login as admin> Click on Site Administration> Plugins> External Tool> Manage Tools> Search for the related tool> Click on "View configuration details" icon

capture1

capture2
回复Jeewani Lakshani

Re: External tools limit exceed in Moodle 3.10

Jake Dallimore -
Core developers的头像 Moodle HQ的头像 Particularly helpful Moodlers的头像 Peer reviewers的头像 Plugin developers的头像 Testers的头像
Thanks, Jeewani.

That is curious. I have a few follow up questions for you:
1. What browser are you using? Can you try another one and see if the problem is resolved?
2. Does that "RangeError" popup show up immediately, or does it only happen after some length of time? (I see you mentioned time limit, hence the question about time)
3. How many tools have you created? Are there hundreds ? Or just the one?
4. What's the exact version of Moodle you're using. It'll be something like 3.10.x, and you can find it at the bottom of the Site admin > Notifications page.

Thanks,
Jake
回复Jake Dallimore

Re: External tools limit exceed in Moodle 3.10

Jeewani Lakshani -
Thank you Jake, Answering to above;
1. What browser are you using? Can you try another one and see if the problem is resolved?

We use Chrome, Firefox, and Microsoft Edge (latest versions) and get the same error for all those browsers.

2. Does that "RangeError" pop up immediately, or does it only happen after some length of time? (I see you mentioned time limit, hence the question about time)

It is appearing after some time. I have attached the HAR file here. Below routes take more time like 43 s apx.

https://3plcgmoodleprd.prd-prsn.com/moodle310/lib/ajax/service.php?sesskey=qjSIcdfxau&info=mod_lti_get_tool_types


pic 2

3. How many tools have you created? Are there hundreds? Or just the one?

Several teams are using this instance and there are hundreds of tools.

4. What's the exact version of Moodle you are using? It will be something like 3.10.x, and you can find it at the bottom of the Site admin > Notifications page.

It is Moodle 3.10.6+ (Build: 20210820)
回复Jeewani Lakshani

Re: External tools limit exceed in Moodle 3.10

Jeewani Lakshani -
Hi Jake any update from your side?
回复Jeewani Lakshani

Re: External tools limit exceed in Moodle 3.10

Jake Dallimore -
Core developers的头像 Moodle HQ的头像 Particularly helpful Moodlers的头像 Peer reviewers的头像 Plugin developers的头像 Testers的头像
Hi Jeewani,

We're all currently very busy with the Moodle 4.0 release preparations, so I've not had any time to attempt replication of this issue yet, especially given the required setup (many, many preconfigureed tools).

Thinking about this issue reminded me of MDL-69092. That adds pagination to that manage tools page to address slowness when dealing with a large number of tools. Since that was an improvement, that's only available in Moodle 4.0 though. I suspect no one ran into a js error on the page when working on that one though, otherwise it would have been classified as a bug and a fix would have been included in the stable versions of Moodle too.

I suspect this occurs for you immediately after you're getting back the response from the web service (which appears to be woefully slow). Then, somewhere is tripping up in the JS with either bad data, or too much data - but I can't be sure until I return similar data on my testing site.