View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006954 | SymmetricDS | Bug | public | 2025-06-18 14:49 | 2025-06-20 20:48 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.15.0 | ||||
| Target Version | 3.15.18 | Fixed in Version | 3.15.18 | ||
| Summary | 0006954: Missing maxFormKeys setting causes "form with too many fields" error | ||||
| 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. | ||||
| Tags | data sync | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-06-18 14:49 | elong | New Issue | |
| 2025-06-18 14:49 | elong | Status | new => assigned |
| 2025-06-18 14:49 | elong | Assigned To | => elong |
| 2025-06-18 14:49 | elong | Tag Attached: data sync | |
| 2025-06-18 14:49 | elong | Issue generated from: 0006904 | |
| 2025-06-18 14:49 | elong | Relationship added | related to 0006904 |
| 2025-06-18 14:52 | elong | Status | assigned => resolved |
| 2025-06-18 14:52 | elong | Resolution | open => fixed |
| 2025-06-18 14:52 | elong | Fixed in Version | => 3.14.18 |
| 2025-06-18 15:00 | admin | Changeset attached | => SymmetricDS 3.15 24373a29 |
| 2025-06-19 12:20 | elong | Fixed in Version | 3.14.18 => 3.15.18 |
| 2025-06-19 12:20 | elong | Target Version | 3.14.18 => 3.15.18 |
| 2025-06-20 20:48 | pbelov | Note Added: 0003123 | |
| 2025-06-20 20:48 | pbelov | Status | resolved => closed |