Bug #27413
open
Upload large file in technique resources or file download returns error
Description
When uploading a 20 Mo file in Resources in a technique, an error is returned.
The procedure described in the documentation https://docs.rudder.io/reference/8.3/administration/webapp.html#_application_server_jetty_configuration has been followed. The number given is enough for the 20 Mo file.
Apache returns this log:[Wed Aug 06 09:01:42.853049 2025] [proxy:error] [pid 2550204:tid 140719142454848] (32)Broken pipe: [client 192.168.254.62:37412] AH01084: pass request body failed to 127.0.0.1:8080 (localhost), referer: https://rudder.lab.rudder.io/rudder/secure/configurationManager/techniqueEditor/technique/etc_hosts_compliance
[Wed Aug 06 09:01:42.853104 2025] [proxy_http:error] [pid 2550204:tid 140719142454848] [client 192.168.254.62:37412] AH01097: pass request body failed to 127.0.0.1:8080 (localhost) from 192.168.254.62 (), referer: https://rudder.lab.rudder.io/rudder/secure/configurationManager/techniqueEditor/technique/etc_hosts_compliance
According to Alexis, the error might come from a problem of timeout for jetty: https://access.redhat.com/solutions/3155451
Files
Updated by François ARMAND 2 days ago
- Subject changed from Upload large file in Resources returns error to Upload large file in technique resources or file download returns error
- Category set to System integration
- Assignee set to Clark ANDRIANASOLO
- Priority changed from To review to 2
So, we need to understand why jetty hand-out so quickly.
We need to go to the root of the problem, especially if it's sync problem jetty and apache - it should not happen. Or not so quickly.
Then, we can choose to set different limit on different case (enhancement):
- in resources, we don't want more than a couple of tens KB (else zipped policies will be hyge and inefficient)
- in shared file, much higher limit.
Updated by
Updated by Clark ANDRIANASOLO 2 days ago
- Related to Bug #25155: Resources upload over 8 MB show error in log and not in UI added