AEMaaCS에서 복제 큐 차단됨

Adobe Experience Manager as a Cloud Service(AEMaaCS)의 복제 큐가 차단되는 경우가 있습니다. 관리자 권한으로 이 문제를 해결하려면 이 문서의 단계에 따르십시오.

설명 description

환경

Adobe Experience Manager as a Cloud Service

문제/증상

javax.jcr.NamespaceException: Unknown namespace prefix: ns22_exception(으)로 인해 AEMaaCS 복제 큐 중 하나가 주기적으로 차단됩니다.

스택 추적:

[ EventAdminAsyncThread #3]  org.apache.sling.distribution.journal.impl.publisher.DistributionPublisher [ null]  Message: Failed attempt (37/infinite) to import the distribution package PackageMessage(pubSlingId=d5e89d11-a40d-4b3f-a8f4-ee478c5b91aa, reqType=ADD, pkgId=dstrpck-1698635668289-1c825ebd-f03d-4d56-97b4-790c169facdc, pkgType=journal_filevault, pkgLength=41118, pubAgentName=publish, userId=replication-service, paths=[ /content/dam/product/photography/129/12999/1299989/PS1299989-731_HB.tif] , deepPaths=[ ] ) at offset=74663574 because of 'javax.jcr.RepositoryException: Some errors occurred while installing packages. Please check the logs for details. First exception is logged as cause.', the importer will retry later,
Stacktrace: org.apache.sling.distribution.common.DistributionException: javax.jcr.RepositoryException: Some errors occurred while installing packages. Please check the logs for details. First exception is logged as cause.
at org.apache.sling.distribution.serialization.impl.vlt.FileVaultContentSerializer.importFromStream(FileVaultContentSerializer.java:159)
at org.apache.sling.distribution.packaging.impl.InMemoryDistributionPackageBuilder.installPackageInternal(InMemoryDistributionPackageBuilder.java:119)
at org.apache.sling.distribution.packaging.impl.AbstractDistributionPackageBuilder.installPackage(AbstractDistributionPackageBuilder.java:156)
at org.apache.sling.distribution.monitor.impl.MonitoringDistributionPackageBuilder.installPackage(MonitoringDistributionPackageBuilder.java:92)
at org.apache.sling.distribution.serialization.impl.vlt.VaultDistributionPackageBuilderFactory.installPackage(VaultDistributionPackageBuilderFactory.java:317)
at org.apache.sling.distribution.journal.bookkeeper.PackageHandler.installAddPackage(PackageHandler.java:78)
at org.apache.sling.distribution.journal.bookkeeper.PackageHandler.apply(PackageHandler.java:61)
at org.apache.sling.distribution.journal.bookkeeper.BookKeeper.importPackage(BookKeeper.java:155)
at org.apache.sling.distribution.journal.impl.subscriber.DistributionSubscriber.processQueueItem(DistributionSubscriber.java:396)
at org.apache.sling.distribution.journal.impl.subscriber.DistributionSubscriber.fetchAndProcessQueueItem(DistributionSubscriber.java:348)
at org.apache.sling.distribution.journal.impl.subscriber.DistributionSubscriber.processQueue(DistributionSubscriber.java:326)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: javax.jcr.RepositoryException: Some errors occurred while installing packages. Please check the logs for details. First exception is logged as cause.
at org.apache.jackrabbit.vault.fs.io.Importer.run(Importer.java:579)
at org.apache.sling.distribution.serialization.impl.vlt.FileVaultContentSerializer.importFromStream(FileVaultContentSerializer.java:151)
... 11 more
Caused by: org.apache.jackrabbit.vault.packaging.PackageException: Error creating/updating node /content/dam/product/photography/129/12999/1299989/PS1299989-731_HB.tif/jcr:content/metadata
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1177)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:976)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
at org.apache.jackrabbit.vault.fs.io.Importer.commit(Importer.java:1018)
at org.apache.jackrabbit.vault.fs.io.Importer.run(Importer.java:531)
... 12 more
Caused by: javax.jcr.NamespaceException: internal error: failed to resolve namespace prefix
at org.apache.jackrabbit.spi.commons.namespace.SessionNamespaceResolver.getURI(SessionNamespaceResolver.java:62)
at org.apache.jackrabbit.spi.commons.conversion.NameParser.parse(NameParser.java:189)
at org.apache.jackrabbit.spi.commons.conversion.ParsingNameResolver.getQName(ParsingNameResolver.java:64)
at org.apache.jackrabbit.spi.commons.conversion.DefaultNamePathResolver.getQName(DefaultNamePathResolver.java:74)
at org.apache.jackrabbit.vault.fs.impl.io.DocViewImporter.updateExistingNode(DocViewImporter.java:1054)
at org.apache.jackrabbit.vault.fs.impl.io.DocViewImporter.addNode(DocViewImporter.java:947)
at org.apache.jackrabbit.vault.fs.impl.io.DocViewImporter.startDocViewNode(DocViewImporter.java:406)
at org.apache.jackrabbit.vault.fs.impl.io.DocViewSAXHandler.startElement(DocViewSAXHandler.java:348)
at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:510)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:374)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2710)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:605)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:534)
at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:888)
at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:824)
at java.xml/com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1216)
at java.xml/com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:635)
at java.xml/com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:324)
at org.apache.jackrabbit.vault.fs.io.DocViewParser.parse(DocViewParser.java:254)
at org.apache.jackrabbit.vault.fs.impl.io.AbstractArtifactHandler.importDocView(AbstractArtifactHandler.j

해결 방법 resolution

골든 게시 배포 큐 UI에서 요청을 삭제하면 큐 차단이 해제됩니다. 아래의 단계를 수행합니다.

  1. 골든 게시 큐를 차단 해제합니다. AEM 시작(으)로 이동 > 도구 > 배포 굵게 표시된 이름의 큐 테이블에서 행을 클릭하여 > 배포 UI.

  2. 다음 페이지에서 차단 항목의 경로(자산일 가능성이 높음)를 식별하고 기록한 다음 을 선택하고 대기열에서 해당 항목을 제거하도록 선택합니다. 이렇게 하면 나머지 활성화가 계속 진행될 수 있습니다.

  3. 이전 단계에서 기록된 경로에 있는 자산으로 이동하여 게시 관리 를 선택합니다. 게시 취소예약: 지금 ​을 선택한 후 다음 을 클릭합니다.

  4. 범위 페이지에서 자산만 선택하고 게시 취소 를 클릭합니다. 참조가 확인되면 계속 을(를) 확인하십시오.

  5. 에셋의 게시가 취소되었음을 확인한 후 에셋으로 다시 이동하여 빠른 Publish 을(를) 선택합니다.

  6. 자산이 성공적으로 게시되었으며 배포 큐가 차단되지 않았는지 확인합니다.

Experience League 캠페인 커뮤니티에서 질문하기

이 주제에 대해 답변하고 싶은 질문이 있거나 이전 답변한 질문을 읽은 경우 이 문서를 포함하는 Experience League 커뮤니티 블로그 게시물을 보고, 질문과 의견을 보내고, Experience League 캠페인 커뮤니티에 참여하세요!

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f