Scarica il pacchetto, https://files.acrobat.com/a/preview/5cacd0b5-55c4-4ca2-832d-86a096c1b842.
Ultimo aggiornamento il
Problema
Quando si eseguono alcune ricerche nell'interfaccia utente Touch di AEM Assets, gli utenti osservano il seguente errore in error.log [1].
09.12.2016 08: 51: 26. 989 *ERROR* [10. 21. 11.46 [1481302285814] GET /mnt/overlay/dam/gui/content/commons/sidepanels, j avax. jcr. PathNotfoundException: jcr: content/metadata at org. apache. jackrabbit.oak. jcr. session .Nodeimpl$7 .perform(Nodelmpl. java: 540) at org. apache. jackrabbit.oak. jcr. session .Nodelmpl$7 .perform(Nodelmpl. java: 534) at org. apache.jackrabbit. oak. j er. delegate. 5essionDelegate. perform(5essionDelegate. java: 200) at org. apache.jackrabbit. oak. j er. session. Itemlmpl. perform(Itemlmpl. j ava: 112) at org. apache.jackrabbit. oak. j er. session. Nodelmpl. getNode (Nodelmpl. j ava: 534) at com. day. cq. dam. c01M1ons. util. UIHelper. get Ti tle(UIHelper. java: 93) at org. apache. jsp. libs. dam. gui. components. admin. childasset. childasset_jsp ._j spService( childasset_j sp. java: 376) at org. apache. sling. scripting. j sp. jasper. runtime. HttpJspBase. service(HttpJspBase. java: 70) at javax. servlet. http.HttpServlet.service(HttpServlet .java: 725) at org. apache. sling. scripting. j sp. jasper. servlet. JspServletWrapper. service( J spServletWrapper. java: 502) at org. apache. sling. scripting. j sp. jasper. servlet. JspServletWrapper. service( J spServletWrapper. java : 449) at org. apache. sling. scripting. j sp. J spSc riptEngineFactory. callJsp( J spScriptEngineFactory. java: 284) at org. apache. sling. scripting. j sp. J spSc riptEngineFactory. access$100(JspScriptEngineFactory. java: 102) at org. apache. sling. scripting. j sp. J spSc riptEngineFactory$J spScriptEngine. eval( JspScriptEngineFactory. java: 536) at org. apache. sling. scripting. core. impl. Defaul tSlingScript. call(Defaul tSlingScript. java: 361) at org. apache. sling. scripting. core. impl. Defaul tSlingScript. eval(Defaul tSlingScript. java: 171) at org. apache. sling. scripting. core. impl. Defaul tSlingScript. service(DefaultSlingScript. java: 463) at org. apache. sling. engine. impl. request. Requestoata. service( RequestData. j ava: 547) at org. apache. sling. engine. impl. filter. SlingComponentFil terChain. render(SlingComponentFil terChain. java: 44) at org. apache. sling. engine. impl. filter. AbstractSl ingFil terChain. dofil ter(AbstractSlingFil terChain. java: 77) at com. day. cq. wcm. core. impl. WO'OeveloperModeFil ter. do Fil ter(WCMDeveloperModeFil ter. java: 117) at org. apache. sling. engine. impl. filter. AbstractSlingfil terChain. do Fil ter(AbstractSlingFil terChain. java: 68) at com. day. cq. wcm. core. impl. WGOebugFil ter. do Fil ter(WCMOebugfi 1 ter. java: 146) at org. apache. sling. engine. impl. filter. AbstractSlingFil terChain. do Fil ter(AbstractSlingFil terChain. java: 68) at com. day. cq. wcm. core. impl. WCMComponentFil ter. fil terRootinclude (WCMComponentFil ter. j ava: 371) at com. day. cq. wcm. core. impl. WCMComponentfil ter. do Fil ter(WCMComponentFil ter. java: 171) at org. apache. sling. engine. impl. filter. AbstractSlingfil terChain. do Fil ter(AbstractSlingFil terChain. java: 68) at com. day. cq. personalization. impl. TargetComponentFilter. doFilter(TargetComponentfilter. java: 96) at org. apache. sling. engine. impl. filter. AbstractSl ingfil terChain. do Fil ter(AbstractSlingFil terChain. java: 68) at org. apache. sling. engine. impl. SlingRequestProcessorimpl. processComponent(SlingRequestProcessorimpl. java: 282)
Causa
Alcune risorse hanno un nodo di metadati mancanti, che interrompe l'interfaccia utente di AEM Assets.
Risoluzione
Per risolvere questo problema, eseguire uno script che riaggiunge i nodi di metadati mancanti ed esegue nuovamente il flusso di lavoro di DAM Update Asset.
-
-
Vai su http://aem-hosl:/port/crx/packmgrfindex.jsp, e accedi come amministratore.
-
Carica il file zip del pacchetto dal passaggio 1, e installalo.
-
Vai a http://aem-hosl:port/apps/tools/components/fixAssets/run.html.
-
Immettere il percorso desiderato in /contenVdam e aggiornare il percorso Workflow Model se si dispone di un modello di flusso di lavoro personalizzato DAM Update Asset.
-
Fai clic su "start". Se si avvia con successo, sotto il tasto "start" viene visualizzato il messaggio "running" [1].
-
L'output viene registrato nel file error.log come segue:
09.02.2017 16:35:51.186 *INFO* [Thread-274] org.apache.jsp.apps.tools.components.fixAssets.POST_jsp$FixAssetsThread Running assets fix. 09.02.2017 16:35:51.289 *INFO* [Thread-274] org.apache.jsp.apps.tools.components.fixAssets.POST_jsp$FixAssetsThread Traversing folder: /content/dam/geometrixx 09.02.2017 16:35:51.390 *INFO* [Thread-274] org.apache.jsp.apps.tools.components.fixAssets.POST_jsp$FixAssetsThread Traversing folder: /content/dam/geometrixx/portraits 09.02.2017 16:36:05.091 *INFO* [Thread-274] org.apache.jsp.apps.tools.components.fixAssets.POST_jsp$FixAssetsThread fixAssets completed, total time: 13905ms
[1] Script "running"
Accedi al tuo account