Expand my Community achievements bar.

July 31st AEM Gems Webinar: Elevate your AEM development to master the integration of private GitHub repositories within AEM Cloud Manager.

Error Cropping image in DAM

Avatar

Level 1

Running AEM6 with SP2 installed.

 

I'm having an issue with cropping an image in the DAM. Here's the error:

 

01.03.2015 09:46:05.600 *INFO* [10.200.61.43 [1425224765333] POST /content/dam/geometrixx-outdoors/error_page.jpg.assetimage.html HTTP/1.1] com.day.cq.dam.core.impl.servlet.ImageModificationServlet created revision [35bf9551-698d-4a37-86f7-00d3055e9462] with label [Before cq5dam.cropped.382.96.1106.731.rotated.0.jpg] for asset [/content/dam/geometrixx-outdoors/error_page.jpg] due to imminent original change.
01.03.2015 09:46:05.603 *INFO* [10.200.61.43 [1425224765333] POST /content/dam/geometrixx-outdoors/error_page.jpg.assetimage.html HTTP/1.1] com.adobe.xmp.worker.files.ncomm.XMPFilesNComm [PERF][EXECUTE_START] | /tmp/10.200.61.435065268103710010906.xmptmp/cqxmp | XMP extraction
01.03.2015 09:46:05.604 *ERROR* [10.200.61.43 [1425224765333] POST /content/dam/geometrixx-outdoors/error_page.jpg.assetimage.html HTTP/1.1] com.day.cq.dam.core.impl.servlet.ImageModificationServlet Error while creating new rendition
java.io.IOException: NativeService disposed <XMPFilesNComm>
        at com.day.cq.dam.core.impl.handler.xmp.NCommXMPHandler.getXmpBytes(NCommXMPHandler.java:155)
        at com.day.cq.dam.core.impl.handler.xmp.NCommXMPHandler.readXmp(NCommXMPHandler.java:121)
        at com.day.cq.dam.core.impl.servlet.ImageModificationServlet.doPost(ImageModificationServlet.java:186)
        at org.apache.sling.api.servlets.SlingAllMethodsServlet.mayService(SlingAllMethodsServlet.java:148)
        at org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:344)
        at org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:375)
        at org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:533)

 

 

According to this post, this problem was fixed in SP2, but we have it installed and the error is still happening on all assets.

http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

 

Thoughts?

 

-Stopp

0 Replies