Expand my Community achievements bar.

SOLVED

Service outage when saving changes from content fragment

Avatar

Level 4

Would like to ask, when we are saving a content fragment, we're experiencing Sevice outage with this messages on the logs:

POST <contentfragment path>.cfm.edit.json HTTP/1.1] com.adobe.cq.assetcompute.impl.assetprocessor.AssetProcessorImpl Failed to initiate process for asset=<contentfragment path>\njava.lang.IllegalArgumentException: Asset without original rendition: <contentfragment path>\n\tat com.adobe.cq.assetcompute.impl.assetprocessor.AssetProcessorInitService.initiateProcess(AssetProcessorInitService.java:65) [com.adobe.cq.dam.cq-dam-processor-nui:1.1.840]\n\tat com.adobe.cq.assetcompute.impl.assetprocessor.AssetProcessorImpl.processAsset(AssetProcessorImpl.java:139) [com.adobe.cq.dam.cq-dam-processor-nui:1.1.840]\n\tat com.adobe.cq.assetcompute.impl.assetprocessor.AssetProcessorImpl.processAsset(AssetProcessorImpl.java:116) [com.adobe.cq.dam.cq-dam-processor-nui:1.1.840]\n\tat com.adobe.cq.dam.cfm.impl.servlets.EditSessionServlet.triggerCFAssetProcessing(EditSessionServlet.java:155) [com.adobe.dam.cq-dam-cfm-impl:0.12.392]\n\tat com.adobe.cq.dam.cfm.impl.servlets.EditSessionServlet.applyEdit(EditSessionServlet.java:130) [com.adobe.dam.cq-dam-cfm-impl:0.12.392]\n\tat com.adobe.cq.dam.cfm.impl.servlets.EditSessionServlet.doPost(EditSessionServlet.java:226) [com.adobe.dam.cq-dam-cfm-impl:0.12.392]\n\tat org.apache.sling.api.servlets.SlingAllMethodsServlet.mayService(SlingAllMethodsServlet.java:146) [org.apache.sling.api:2.27.2]\n\tat org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:342) [org.apache.sling.api:2.27.2]\n\tat org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:374) [org.apache.sling.api:2.27.2]\n\tat org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:544) [org.apache.sling.engine:2.15.16]\n\tat org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:44) [org.apache.sling.engine:2.15.16]\n\tat org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:88) [org.apache.sling.engine:2.15.16]\n\tat com.day.cq.wcm.core.impl.WCMDebugFilter.doFilter(WCMDebugFilter.java:138) [com.day.cq.wcm.cq-wcm-core:5.14.174]\n\tat org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:78) [org.apache.sling.engine:2.15.16]\n\tat com.adobe.cq.dam.cfm.ui.impl.EditorCacheFilter.doFilter(EditorCacheFilter.java:102) [com.adobe.dam.cq-dam-cfm-impl:0.12.392]\n\tat org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:78) [org.apache.sling.engine:2.15.16]\n\tat com.adobe.granite.metrics.knownerrors.impl.ErrorLoggingComponentFilter.doFilter(ErrorLoggingComponentFilter.java:71) [com.adobe.granite.metrics.knownerrors:0.0.24]\n\tat org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:78) [org.apache.sling.engine:2.15.16]\n\tat org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:84) [org.apache.sling.engine:2.15.16]\n\tat com.day.cq.wcm.core.impl.WCMComponentFilter.filterRootInclude(WCMComponentFilter.java:375) [com.day.cq.wcm.cq-wcm-core:5.14.174]\n\tat com.day.cq.wcm.core.impl.WCMComponentFilter.doFilter(WCMComponentFilter.java:190) [com.day.cq.wcm.cq-wcm-core:5.14.174]\n\tat org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:78) [org.apache.sling.engine:2.15.16]\n\tat com.day.cq.wcm.core.impl.page.PageLockFilter.doFilter(PageLockFilter.java:91) [com.day.cq.wcm.cq-wcm-core:5.14.174]\n\tat org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:78) [org.apache.sling.engine:2.15.16]\n\tat com.day.cq.personalization.impl.TargetComponentFilter.doFilter(TargetComponentFilter.java:94) [com.day.cq.cq-personalization:5.13.62]\n\tat org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:78) [org.apache.sling.engine:2.15.16]\n\tat org.apache.sling.engine.impl.SlingRequestProcessorImpl.processComponent(SlingRequestProcessorImpl.java:374) [org.apache.slin\n MESSAGE TOO LONG, TRUNCATED THE BODY \n 5.1.22]\n\tat org.apache.felix.http.base.internal.dispatch.DispatcherServlet.service(DispatcherServlet.java:49) [org.apache.felix.http.jetty:5.1.22]\n\tat jakarta.servlet.http.HttpServlet.service(HttpServlet.java:587) [org.apache.felix.http.servlet-api:2.1.0]\n\tat org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:529) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1580) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:221) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1381) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:176) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:484) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1553) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:174) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1303) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:129) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:149) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.handler.StatisticsHandler.handle(StatisticsHandler.java:173) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.Server.handle(Server.java:563) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.HttpChannel$RequestDispatchable.dispatch(HttpChannel.java:1598) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:753) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:501) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:287) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:314) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:421) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:390) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:277) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.run(AdaptiveExecutionStrategy.java:199) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:411) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:969) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.doRunJob(QueuedThreadPool.java:1194) [org.apache.felix.http.jetty:5.1.22]\n\tat org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1149) [org.apache.felix.http.jetty:5.1.22]\n\tat java.base/java.lang.Thread.run(Thread.java:834)

What would be the cause of it and possible fix. Thanks!

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi,

 

I assume you are using AEM as a Cloud Service (AEMaaCS). Since AEM 6.5.10, Content Fragments are not expected to have an original rendition, though I’m not certain when this change was implemented in the Cloud version, but for sure this is true for Cloud as well. You can find a helpful explanation here: link.

I was able to reproduce the issue you’re seeing in the logs, but I didn’t experience any outage myself. If you are encountering an outage, it may not be directly related to the stack trace in the logs. Could you please check if there are any other relevant details? Maybe there is a reindex process kicking off or something related to MSM that can be causing the outage.

 

Hope this helps



Esteban Bustamante

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

Hi,

 

I assume you are using AEM as a Cloud Service (AEMaaCS). Since AEM 6.5.10, Content Fragments are not expected to have an original rendition, though I’m not certain when this change was implemented in the Cloud version, but for sure this is true for Cloud as well. You can find a helpful explanation here: link.

I was able to reproduce the issue you’re seeing in the logs, but I didn’t experience any outage myself. If you are encountering an outage, it may not be directly related to the stack trace in the logs. Could you please check if there are any other relevant details? Maybe there is a reindex process kicking off or something related to MSM that can be causing the outage.

 

Hope this helps



Esteban Bustamante

Avatar

Administrator

@LyonMartin Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!



Kautuk Sahni