Expand my Community achievements bar.

SOLVED

XMPWritebackProcess Disposal Leads to System Failure

Avatar

Former Community Member
We've experienced an issue 4 times now where once the XMPWritebackProcess "NativeService" disposes, the XMPWritebackProcess workflow continues down a continually looping process of starting and getting disposed.
One such error statement that indicates the disposal occurring is
 
 *ERROR* [JobHandler: /etc/workflow/instances/****-0*-0*/model_15800907609329186:/content/dam/jofa/issues/2015/apr/closing-the-skills-gap.pdf/jcr:content/metadata] com.day.cq.dam.core.process.XMPWritebackProcess NativeService disposed <XMPFilesNComm>
 
When this issue is left unattended, the JCR Repository continually grows at a rapid pace and eventually the system goes down from running out of disk space.
Of the 4 times the issue has occurred, 3 instances were from PDFs and the 4th instance that occurred is from a .jpg file.
 
Included is a portion of the AEM error.log file from when one of the incidents started.
 

*INFO* [JobHandler: /etc/workflow/instances/2015-04-07/model_15796299302211746:/content/dam/newsletters/insiders/article-images/busy-season-43x57.jpg/jcr:content/metadata] com.adobe.xmp.worker.files.ncomm.XMPFilesNComm [PERF][EXECUTE_START] | /tmp/JobHandler903672582835847718.xmptmp/cqxmp | XMP injection
07.04.2015 13:51:20.697 *ERROR* [JobHandler: /etc/workflow/instances/2015-04-07/model_15796299302211746:/content/dam/newsletters/insiders/article-images/busy-season-43x57.jpg/jcr:content/metadata] com.day.cq.dam.core.process.XMPWritebackProcess NativeService disposed <XMPFilesNComm>
07.04.2015 13:51:20.856 *INFO* [JobHandler: /etc/workflow/instances/2015-04-07/model_15796299380588545:/content/dam/newsletters/insiders/article-images/busy-season-43x57.jpg/jcr:content/renditions/original] com.day.cq.dam.video.FFMpegThumbnailProcess execute: asset [/content/dam/newsletters/insiders/article-images/busy-season-43x57.jpg] is not of a video mime type, asset ignored.

 
 
We would like to know if there is a solution available to prevent this issue from occurring again.
1 Accepted Solution

Avatar

Correct answer by
Level 2
2 Replies

Avatar

Correct answer by
Level 2

Avatar

Level 1

Is there a similar fix for Windows Server 2013? I'm getting the same errors.