[ 
https://issues.apache.org/jira/browse/IMAGING-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

aditya seth updated IMAGING-307:
--------------------------------
    Summary: Apache Commons imaging AEM Image upload issue - Invalid block size 
 (was: CLONE - Apache Commons imaging AEM Image upload issue - Invalid block 
size)

> Apache Commons imaging AEM Image upload issue - Invalid block size
> ------------------------------------------------------------------
>
>                 Key: IMAGING-307
>                 URL: https://issues.apache.org/jira/browse/IMAGING-307
>             Project: Commons Imaging
>          Issue Type: Bug
>          Components: Format: JPEG
>            Reporter: aditya seth
>            Priority: Critical
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> We are trying to upload some assets to AEM DAM which is using the apache 
> commons imaging bundle (version 1.0.0.R1725432-B002) to verify and ingest the 
> assets. Some of the assets are being rejected wit the below error:
>  
> 20.07.2020 13:18:57.769 *WARN* [JobHandler: 
> /var/workflow/instances/server0/2020-07-16_1/tsc_dam_product_update_asset_852:/content/dam/tsc/product/149632099_A1.jpg/jcr:content/renditions/original]
>  com.day.cq.dam.commons.handler.StandardImageHandler extractMetadata: cannot 
> read metadata from image [/content/dam/tsc/product/149632099_A1.jpg]:
> org.apache.commons.imaging.ImageReadException: Invalid Block Size : 83252 > 
> 65504
>         at 
> org.apache.commons.imaging.formats.jpeg.iptc.IptcParser.parseAllBlocks(IptcParser.java:357)
>  [org.apache.commons.commons-imaging:1.0.0.R1725432-B002]
>  
> The API being used is 
> [https://github.com/apache/commons-imaging/blob/commons-imaging-1.0-RC1/src/main/java/org/apache/commons/imaging/formats/jpeg/iptc/IptcParser.java#L321]
>  
> Can you please let me know why is this error happening, and what needs to be 
> done to the image to get it pass through this error. Are there any specific 
> image parameters or metedata which needs to be changed to get this corrected. 
> I have attached one image which is having this issue. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to