View Revisions: Issue #6904
| Summary | 0006904: Missing maxFormKeys setting causes "form with too many fields" error | ||
|---|---|---|---|
| Revision | 2025-05-23 19:06 by elong | ||
| Description | The legacy setting of org.eclipse.jetty.server.Request.maxFormKeys was previously set to 10,000 to allow a large number of batches to be sent and acknowledged at once. After upgrading to Spring Boot, it defaults to only 1,000 form keys. It's also missing the conversion of the old setting into the new Spring Boot application property. When the limit is hit, this is shown in the logs: [ServletApiRequest] [qtp304406966-69] java.util.concurrent.CompletionException: java.lang.IllegalStateException: form with too many fields > 1000 Workaround is to lower the max batches to send on the channel. |
||
| Revision | 2025-06-11 12:11 by elong | ||
| Description | The legacy setting of org.eclipse.jetty.server.Request.maxFormKeys was previously set to 10,000 to allow a large number of batches to be sent and acknowledged at once. After upgrading to Spring Boot, it defaults to only 1,000 form keys. It's also missing the conversion of the old setting into the new Spring Boot application property. When the limit is hit, this is shown in the logs: [ServletApiRequest] [qtp304406966-69] java.util.concurrent.CompletionException: java.lang.IllegalStateException: form with too many fields > 100000 Workaround is to lower the max batches to send on the channel. |
||
| Revision | 2025-06-11 12:13 by elong | ||
| Description | The legacy setting of org.eclipse.jetty.server.Request.maxFormKeys was previously set to 10,000 to allow a large number of batches to be sent and acknowledged at once. After upgrading to Spring Boot, it defaults to only 1,000 form keys. It's also missing the conversion of the old setting into the new Spring Boot application property. When the limit is hit, this is shown in the logs: [ServletApiRequest] [qtp304406966-69] java.util.concurrent.CompletionException: java.lang.IllegalStateException: form with too many fields > 1000 Workaround is to lower the max batches to send on the channel. |
||
| Revision | 2025-06-11 12:14 by elong | ||
| Description | The legacy setting of org.eclipse.jetty.server.Request.maxFormKeys was previously set to 100,000 to allow a large number of batches to be sent and acknowledged at once. After upgrading to Spring Boot, it defaults to only 1,000 form keys. It's also missing the conversion of the old setting into the new Spring Boot application property. When the limit is hit, this is shown in the logs: [ServletApiRequest] [qtp304406966-69] java.util.concurrent.CompletionException: java.lang.IllegalStateException: form with too many fields > 1000 Workaround is to lower the max batches to send on the channel. |
||
| Revision | 2025-05-23 19:06 by elong | ||
| Additional Information | |||
| Revision | 2025-10-02 23:09 by pbelov | ||
| Additional Information | Set this JVM property (on a SymmetricDS node, which is listening for inbound HTTP connections) to the conf/sym_service.conf file: -Dorg.eclipse.jetty.server.Request.maxFormContentSize=800000 -Dorg.eclipse.jetty.server.Request.maxFormKeys=100000 Or to the bin/setenv file, if running SymmetricDS in some other way, like from a command line. |
||
| Revision | 2025-10-02 23:12 by pbelov | ||
| Additional Information | Set this JVM property (on a SymmetricDS node, which is listening for inbound HTTP connections) to the conf/sym_service.conf file (and restart the service): -Dorg.eclipse.jetty.server.Request.maxFormContentSize=800000 -Dorg.eclipse.jetty.server.Request.maxFormKeys=100000 Or to the bin/setenv file, if running SymmetricDS in some other way, like from a command line. |
||