Resolving metadata save failures and UI limits caused by Sling request parameter and rendering configuration limits
Metadata schema updates, folder metadata saves, and multipart form submissions can fail in Adobe Experience Manager when Sling request limits are exceeded. These failures often occur due to restrictions such as maximum request parameters, file count limits, or rendering recursion limits configured in OSGi. As a result, the system may stop processing requests or silently fail to persist changes. Adjusting the relevant Sling and Jetty configuration limits resolves the issue. Increase configuration limits and validate deployment to restore normal functionality.
Description description
Environment
- Adobe Experience Manager as a Cloud Service
- Adobe Experience Manager 6.5 (Managed Services or on-premise)
- AEM Assets Essentials
Issue/Symptoms
- Error log shows parsing failures for multipart POST requests
- Error indicates too many name/value pairs in request parameters
- File count limit exceptions during metadata or move operations
- Metadata schema UI shows successful save but changes do not persist
- GenericList UI fails when the number of items increases significantly
- Multipart form submissions return empty or incomplete parameters
Cause
Sling enforces limits on HTTP request processing to prevent oversized or malicious requests. When metadata schemas, lists, or forms exceed configured thresholds such as parameter count, file count, multipart size, or rendering calls, Sling stops processing the request or fails to render the UI.
How to confirm
- Open logs and search for errors related to multipart parsing or parameter limits
- Check for messages indicating too many parameters or file count exceeded
- Verify if UI actions appear successful but do not persist changes
Resolution resolution
Follow these steps to resolve this issue
- Review logs to identify which limit is exceeded by checking messages related to request parsing, parameter counts, file limits, or rendering calls.
- Increase Sling request parameter limits by updating OSGi configuration for request handling. Set appropriate values for maximum parameters and file counts based on schema size.
- Adjust maximum form size in the HTTP service configuration if multipart POST errors occur.
- Increase the rendering recursion limit to support large lists and prevent UI rendering failures.
- Deploy configuration updates correctly and ensure they apply to the appropriate environment.
- Validate that configuration files are placed in the correct run mode or configuration path and redeploy if necessary.