Offloading Issue in AEM 6.0 | Community
Skip to main content
K
Kaustav_Majoomd
October 16, 2015
Solved

Offloading Issue in AEM 6.0

  • October 16, 2015
  • 6 replies
  • 2129 views

Hi,

I am trying to implement the Offloading mechanism in multiple AEM 6.0(SP1) author instances(non-clustered). The thing I observed is, I can able to connect all of the instances in a topology, but the offloading is not working! I tried using "DAM Upload Asset Offloading" workflow in one instance. Ideally, that image should show up in all the instances which are all connected in the topology. But, it is not happening. Please let me know whether it is a known issue with 6.0, or am I doing something wrong in it? If yes, then kindly send me some links or video links, where I can refer it. Thanks a lot for the help in advance!!

 

Regards,

Kaustav Majoomder

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

It should work, Make sure you configured discovery url correctly. Recoding at [1] though it is for 5.6.1 applies to AEM6 also

[1]  http://dev.day.com/content/ddc/en/gems/introduction-of-job-handling-and-offloading-in-aem-5-6-1-.html

6 replies

Sham_HC
Sham_HCAccepted solution
October 16, 2015

It should work, Make sure you configured discovery url correctly. Recoding at [1] though it is for 5.6.1 applies to AEM6 also

[1]  http://dev.day.com/content/ddc/en/gems/introduction-of-job-handling-and-offloading-in-aem-5-6-1-.html

K
Kaustav_MajoomdAuthor
October 16, 2015

I am getting the below error while trying to Offload two author instances:

04.12.2014 11:28:34.565 *INFO* [JobHandler: /etc/workflow/instances/2014-12-04/model_5840153182794:/content/dam/projects/gov/BionADE-FINAL.jpg/jcr:content/renditions/original] com.day.cq.dam.core.process.CommandLineProcess execute: mime type [image/jpeg] of asset [/content/dam/projects/gov/BionADE-FINAL.jpg] is not in list of accepted mime types [[image/eps, image/x-eps, application/postscript, application/eps, application/x-eps]], ignoring.
04.12.2014 11:28:34.565 *INFO* [JobHandler: /etc/workflow/instances/2014-12-04/model_5840153182794:/content/dam/projects/gov/BionADE-FINAL.jpg/jcr:content/renditions/original] com.day.cq.dam.video.FFMpegTranscodeProcess execute: asset [/content/dam/projects/gov/BionADE-FINAL.jpg] is not of a video mime type, asset ignored.
04.12.2014 11:28:35.990 *INFO* [JobHandler: /etc/workflow/instances/2014-12-04/model_5840153182794:/content/dam/projects/gov/BionADE-FINAL.jpg/jcr:content/renditions/original] com.day.cq.dam.core.impl.RenditionMakerImpl generated rendition: /content/dam/projects/gov/BionADE-FINAL.jpg/jcr:content/renditions/cq5dam.web.1280.1280.jpeg
04.12.2014 11:28:36.108 *INFO* [JobHandler: /etc/workflow/instances/2014-12-04/model_5840153182794:/content/dam/projects/gov/BionADE-FINAL.jpg/jcr:content/renditions/original] com.day.cq.dam.s7dam.common.process.VideoProxyServiceProcess Skipping VideoProxyServiceProcess Step
04.12.2014 11:28:36.114 *INFO* [JobHandler: /etc/workflow/instances/2014-12-04/model_5840153182794:/content/dam/projects/gov/BionADE-FINAL.jpg/jcr:content/renditions/original] com.day.cq.dam.pim.impl.sourcing.upload.process.ProductAssetsUploadProcess payload path :/content/dam/projects/gov/BionADE-FINAL.jpg/jcr:content/renditions/original
04.12.2014 11:28:36.185 *INFO* [JobHandler: /etc/workflow/instances/2014-12-04/model_5872256642722:/content/dam/projects/gov/BionADE-FINAL.jpg/jcr:content/metadata] com.day.cq.dam.core.process.XMPWritebackProcess payload path :/content/dam/projects/gov/BionADE-FINAL.jpg/jcr:content/metadata
04.12.2014 11:28:43.981 *ERROR* [Thread-125] com.day.cq.commons.ImageHelper Error while creating layer.
04.12.2014 11:28:43.997 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 Sending GET request to http://10.101.141.147:4502/bin/receive?sling:authRequestLogin=1
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 sent. Response: 200 OK
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 ------------------------------------------------
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 Sending message to 10.101.141.147:4502
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 >> GET /bin/receive?sling:authRequestLogin=1 HTTP/1.0
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 >> Action: Internal Poll
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 >> Path: 
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 >> Handle: 
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 --
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 << HTTP/1.1 200 OK
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 << Date: Thu, 04 Dec 2014 05:58:44 GMT
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 << Content-Type: application/octet-stream
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 << Content-Length: 32
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 << Server: Jetty(8.1.14.v20131031)
04.12.2014 11:28:44.106 *INFO* [pool-9-thread-2] com.day.cq.replication.Agent.offloading_reverse_db467b7d-7722-4f50-8d7a-33c8dbafd050 Message sent.

Please help me on this..

 

Regards,

Kaustav Majoomder

Sham_HC
Sham_HC
October 16, 2015

Hi Kaustav Majoomder,

  I do not see any issue with topology setup here.  The image wit hall renditions will be visible in primary server once workflow completes in offloading server. From logs seeing error in completing workflow step. Fix the same.
 
 
Thanks,
Sham
Twitter: @adobe_sham

K
Kaustav_MajoomdAuthor
October 16, 2015

Hi Sham,

Thanks for the help!!

I have already referred the previous video link. But, still am unable to do it sad. Can you please describe about the discovery url setup. I have configured the topology connector url in the felix console so far. 

 

Regards,

Kaustav Majoomder

K
Kaustav_MajoomdAuthor
October 16, 2015

Thanks Sham for the analysis!!

Can you kindly let me know what exactly I have fix in the workflow module. As because, I didn't created any custom workflow. I am using the default workflow only, which has been provided for Offloading i.e. "DAM Update Asset Offloading". Please let me know, is there is any bug in this workflow itself?

 

Regards,

Kaustav Majoomder

Sham_HC
Sham_HC
October 16, 2015

Kaustav Majoomder wrote...

Thanks Sham for the analysis!!

Can you kindly let me know what exactly I have fix in the workflow module. As because, I didn't created any custom workflow. I am using the default workflow only, which has been provided for Offloading i.e. "DAM Update Asset Offloading". Please let me know, is there is any bug in this workflow itself?

 

Regards,

Kaustav Majoomder

 

Hi Kaustav Majoomder,

   I have noticied [1], general possibility are image dimesion is outside rastor size OR a hidden object in asset Or a product bug. File an daycare along with asset to investigate the case.

[1] Error while creating layer

Thanks,

Tweet @adobe_sham

Terms & ConditionsAccessibility statement

Loading footer...