Tomcat maxPartCount
17 views
Skip to first unread message
Sam Ottenhoff
Mar 4, 2026, 4:59:19 PM (2 days ago) Mar 4
to sakai-dev
Tomcat now enforces multipart part-count limits via Connector property maxPartCount (in addition to maxParameterCount).
Important defaults:
- Tomcat 9.0.106: maxPartCount default is 10
- Tomcat 9.0.107+: maxPartCount default is 50
If a Samigo submission exceeds this limit, request parsing can fail before normal app handling.
In Sakai this is especially easy to trigger in Samigo “take assessment via URL” flows, including launches from Lessons (which use the via-URL path). Symptom: user clicks submit/save, does not advance to confirmation, and responses do not persist.
Important defaults:
- Tomcat 9.0.106: maxPartCount default is 10
- Tomcat 9.0.107+: maxPartCount default is 50
If a Samigo submission exceeds this limit, request parsing can fail before normal app handling.
In Sakai this is especially easy to trigger in Samigo “take assessment via URL” flows, including launches from Lessons (which use the via-URL path). Symptom: user clicks submit/save, does not advance to confirmation, and responses do not persist.
Example Connector tuning:
<Connector
...
maxParameterCount="10000"
maxPartCount="2000" />
<Connector
...
maxParameterCount="10000"
maxPartCount="2000" />
I also recommend enabling the Tomcat FailedRequestFilter so failures are rejected clearly instead of failing ambiguously.
--Sam
Reply all
Reply to author
Forward
0 new messages