Hello,
I am encountering the following error while trying to access an image that uses the AdaptiveImageServlet. If anyone has experienced this issue before, please share the resolution or suggestions to address it. The AEM version in use is 6.5 SP22.
Here’s what I’ve checked so far:
Error log:
23.06.2025 13:10:22.000 *ERROR* [198.203.175.233 [1750684221990] GET /content/brand/en/test/_jcr_content/root/layout_container_619122462/content/xx/content/layout_container/content/image.coreimg.85.1200.png/1750339300167/testimg.png HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught IOException
java.io.IOException: Cannot process rendition original due to size null
at com.adobe.cq.wcm.core.components.internal.servlets.AdaptiveImageServlet.filter(AdaptiveImageServlet.java:596) [com.adobe.cq.core.wcm.components.core:2.27.0]
at com.adobe.cq.wcm.core.components.internal.servlets.AdaptiveImageServlet.getOriginal(AdaptiveImageServlet.java:576) [com.adobe.cq.core.wcm.components.core:2.27.0]
at com.adobe.cq.wcm.core.components.internal.servlets.AdaptiveImageServlet.getBestRendition(AdaptiveImageServlet.java:526) [com.adobe.cq.core.wcm.components.core:2.27.0]
at com.adobe.cq.wcm.core.components.internal.servlets.AdaptiveImageServlet.transformAndStreamAsset(AdaptiveImageServlet.java:339) [com.adobe.cq.core.wcm.components.core:2.27.0]
at com.adobe.cq.wcm.core.components.internal.servlets.AdaptiveImageServlet.doGet(AdaptiveImageServlet.java:236) [com.adobe.cq.core.wcm.components.core:2.27.0]
Views
Replies
Total Likes
Hi @test1234567
Indicates that the AdaptiveImageServlet cannot determine the size of the original rendition of the image. This is a known issue that can happen even when the image looks fine in DAM and all renditions exist. Here's how you can troubleshoot and resolve it:
Missing or Incomplete Binary Data
The original rendition's binary might be missing or inaccessible despite showing in DAM.
Sometimes AEM stores only metadata, and the binary could be missing due to a failed upload, replication issue, or packaging error.
Inconsistent or Corrupt Metadata
The metadata for the original rendition might not include a valid jcr:content/metadata node with tiff:ImageWidth or dam:PhysicalWidth properties.
This makes it impossible for AdaptiveImageServlet to determine image dimensions.
Asset Not Fully Processed
If AEM’s asset workflow (DAM Update Asset) didn't fully run or was interrupted, the renditions or metadata could be incomplete.
Check Original Rendition Exists
Go to CRXDE: /content/dam/your/image/path/jcr:content/renditions/original
Confirm that a binary node named jcr:content with a jcr:data property exists.
Also verify the jcr:mimeType is set correctly.
Verify Metadata
At /content/dam/your/image/path/jcr:content/metadata, check for:
tiff:ImageWidth
tiff:ImageLength
dam:PhysicalWidth
dam:PhysicalHeight
If any are missing, AdaptiveImageServlet may fail.
Re-run DAM Update Asset Workflow
Right-click the asset in DAM → Workflow → Reprocess Asset
Alternatively, trigger the DAM Update Asset workflow manually via /libs/cq/workflow/content/console.html.
Compare to Working Environment
Compare the metadata node and renditions structure in CRXDE with a working asset/environment.
Especially check:
Size properties in metadata
Rendition structure
Binary size (jcr:data) on original rendition.
Re-upload the Image
Delete the image from DAM, re-upload it, and confirm the asset workflow completes.
Check that metadata and renditions regenerate correctly.
Replace the Original Rendition
If the original rendition is corrupt, overwrite it using a tool like vlt, CRXDE, or repackage the asset correctly.
Manually Add Metadata (Not Recommended Unless Temporary)
If the metadata is missing but you know the actual dimensions, you could manually add:
tiff:ImageWidth = 1200
tiff:ImageLength = 800
Only do this to verify if metadata is the problem; not a permanent fix.
Hope this helpful
Regards,
Karishma.
@test1234567 Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies