Samigo/Tomcat fails viewing submission with huge amount of them
Description
Activity
Mark Golbeck August 27, 2024 at 8:52 AM
Since it's been over two years without any further information provided, we're closing this Jira issue for now. If more details become available in the future, we can reopen it. Thank you.
Matthew Jones November 3, 2017 at 8:31 AM
No, sounds like https://sakaiproject.atlassian.net/browse/SAK-25677#icft=SAK-25677 improved things but this is still incomplete. It also sounds like Rutgers has/had a patch to improve this one but I don't see that it was ever contributed.
Benjamin Rappleyea November 3, 2017 at 8:20 AM
It appears to be some time since this was JIRA was updated. Has JIRA https://sakaiproject.atlassian.net/browse/SAK-25677#icft=SAK-25677 incorporated a fix for this issue?
Charles Hedrick June 30, 2016 at 11:14 AM
I looked back at the discussion for SAK-25677. I think that was the wrong decision. Memory is not that expensive. I'd rather use more memory if it would buy faster response, less bandwidth, and (probably) better security.
Charles Hedrick June 30, 2016 at 10:08 AMEdited
We have a site with 17,000 submissions for a test. With this patch, and with
maxPostSize="50000000"
in server.xml, we can load the page in about a minute the first time. It takes about 10 sec to move to a new page or search for a user.
I can't quite see how we could come up with a larger case than this, so that's going to be the limit of our tuning.
To do better than this we'd need to redo a couple of beans so they only fetch the data that they need for the specific page they're displaying. Currently it fetches all the data and then pages through it. This wouldn't be a difficult project, as the changes are pretty localized.
Details
Details
Priority
Major
The set the scene....
We're now having all placement testing at Rutgers being done through Sakai, this means that we have thousands (currently highest is 5300+) submissions in Samigo.
We noticed a problem that when trying to view submissions for a particular student when there are a HUGE amount of submissions causes a Tomcat error.(thousands)
We got a
INFO: More than the maximum number of request parameters (GET plus POST) for a single request ([10,000]) were detected. Any parameters beyond this limit have been ignored. To change this limit, set the maxParameterCount attribute on the Connector.
Error
Got a way to fix it from this SO link.
https://stackoverflow.com/questions/17105549/set-the-maxparametercount-attribute-on-the-connector
I believe this is because of the way Samigo handles edits/links on the page. Instead of just getting the info for a single user when you click their name, it does a giant post request with parameters for every user on that page.
Perhaps it should be that if you click a single users name, it does a GET for just that user.