Oauth integration with azure portal is not working in AEM 6.3 | Community
Skip to main content
varunr40033127
New Participant
May 23, 2019 7:39 AM UTC
Solved

Oauth integration with azure portal is not working in AEM 6.3

Hi ,

Oauth integration with azure portal is not working in AEM 6.3 SP3 but working in AEM 6.1.

Error Logs for the same:

java.lang.UnsupportedOperationException: The query read or traversed more than 100000 nodes. To avoid affecting other tasks, processing was stopped.

at org.apache.jackrabbit.oak.query.FilterIterators.checkReadLimit(FilterIterators.java:66)

at org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor.fetchNext(Cursors.java:331)

at org.apache.jackrabbit.oak.spi.query.Cursors$TraversingCursor.next(Cursors.java:310)

at org.apache.jackrabbit.oak.query.ast.SelectorImpl.next(SelectorImpl.java:422)

at org.apache.jackrabbit.oak.query.QueryImpl$RowIterator.fetchNext(QueryImpl.java:844)

at org.apache.jackrabbit.oak.query.QueryImpl$RowIterator.hasNext(QueryImpl.java:869)

at com.google.common.collect.TransformedIterator.hasNext(TransformedIterator.java:43)

at com.google.common.collect.Iterators$7.computeNext(Iterators.java:645)

at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143)

at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138)

at com.google.common.collect.TransformedIterator.hasNext(TransformedIterator.java:43)

at com.adobe.granite.auth.oauth.impl.helper.OAuthHelper.getCRXUserByOAuthId(OAuthHelper.java:633)

at com.adobe.granite.auth.oauth.impl.helper.OAuthHelper.createOrUpdateCRXUser(OAuthHelper.java:510)

at com.adobe.granite.auth.oauth.impl.helper.OAuthHelper.createOrUpdateCRXUser(OAuthHelper.java:492)

at com.adobe.granite.auth.oauth.impl.helper.OAuthHelper.createOrUpdateCRXUser(OAuthHelper.java:480)

at com.adobe.granite.auth.oauth.impl.OAuthAuthenticationHandler.extractCredentials(OAuthAuthenticationHandler.java:231)

at org.apache.sling.auth.core.impl.AuthenticationHandlerHolder.doExtractCredentials(AuthenticationHandlerHolder.java:76)

at org.apache.sling.auth.core.impl.AbstractAuthenticationHandlerHolder.extractCredentials(AbstractAuthenticationHandlerHolder.java:60)

at org.apache.sling.auth.core.impl.SlingAuthenticator.getAuthenticationInfo(SlingAuthenticator.java:735)

at org.apache.sling.auth.core.impl.SlingAuthenticator.doHandleSecurity(SlingAuthenticator.java:483)

at org.apache.sling.auth.core.impl.SlingAuthenticator.handleSecurity(SlingAuthenticator.java:460)

at org.apache.sling.engine.impl.SlingHttpContext.handleSecurity(SlingHttpContext.java:131)

at org.apache.felix.http.base.internal.whiteboard.PerBundleServletContextImpl.handleSecurity(PerBundleServletContextImpl.java:82)

at org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:58)

at org.apache.felix.http.base.internal.dispatch.Dispatcher$1.doFilter(Dispatcher.java:146)

at org.apache.felix.http.base.internal.whiteboard.WhiteboardManager.invokePreprocessors(WhiteboardManager.java:1000)

at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:91)

at org.apache.felix.http.base.internal.dispatch.DispatcherServlet.service(DispatcherServlet.java:49)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)

at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865)

at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:535)

at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)

at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)

at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)

at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340)

at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)

at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)

at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)

at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)

at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242)

at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)

at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:220)

at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)

at org.eclipse.jetty.server.Server.handle(Server.java:503)

at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364)

at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)

at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)

at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)

at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)

at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)

at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)

at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)

at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)

at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)

at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)

at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)

at java.lang.Thread.run(Thread.java:748)

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Hamid1350Accepted solution
Employee
Jun 17, 2019 6:32 PM UTC

Ref: The query read or traversed more than 100000 nodes. To avoid affecting other tasks, processing was stopped.

This seems to be an issue with many nodes to traverse. Check the log to find the problematic query and create an index. you can use Oak Index Definition Generator: Oak Utilities : Index Definition Generator​. So basically you find the problematic query in the "error.log" and put it in "Index Definition Generator". The tool should return an index definition that should be created in order to avoid traversal query situation.

View reply

2 replies

akhilraj
akhilraj
Level 5
Dec 27, 2022 7:00 AM UTC

Hi @varunr40033127 :

Have you completed the oauth integration with Azure provider ?

Translate
Hamid1350Accepted solution
Employee
Jun 17, 2019 6:32 PM UTC

Ref: The query read or traversed more than 100000 nodes. To avoid affecting other tasks, processing was stopped.

This seems to be an issue with many nodes to traverse. Check the log to find the problematic query and create an index. you can use Oak Index Definition Generator: Oak Utilities : Index Definition Generator​. So basically you find the problematic query in the "error.log" and put it in "Index Definition Generator". The tool should return an index definition that should be created in order to avoid traversal query situation.

Translate
Terms & ConditionsAccessibility statement

Loading footer...