Hi,I am seeing following errors in log (AEM 6.3)org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 4 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.java.lang.Exception: The session was created here:Can any one tell me, why i am getting these session idle , refresh strategy errors in logs and how to resolve this issue?Thanks,Sri

sreenu539

Level 7

Solved

refresh strategy errors in log AEM 6.3

12 replies
6681 views
Translate All

Hi,

I am seeing following errors in log (AEM 6.3)

org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 4 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.
java.lang.Exception: The session was created here:

Can any one tell me, why i am getting these session idle , refresh strategy errors in logs and how to resolve this issue?

Thanks,

Sri

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

joerghohAccepted solution

Adobe Employee

ok, let's see.

In the first stacktrace I see this:

at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.getParentResourceType(Resourc eResolverImpl.java:1216)

at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.isResourceType(ResourceResolv erImpl.java:1239)

at com.adobe.cq.social.scf.core.resourcetree.ResourceTypeTree$RTree.insert(ResourceTypeTree. java:108)

at com.adobe.cq.social.scf.core.resourcetree.ResourceTypeTree$RTree.put(ResourceTypeTree.java:96)

and in the second one

at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.getParentResourceType(Resourc eResolverImpl.java:1205)

at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.isResourceType(ResourceResolv erImpl.java:1233)

at org.apache.sling.api.resource.AbstractResource.isResourceType(AbstractResource.java:121)

at org.apache.sling.api.resource.ResourceWrapper.isResourceType(ResourceWrapper.java:171)

at org.apache.sling.i18n.impl.JcrResourceBundleProvider.isDictionaryResource(JcrResourceBund leProvider.java:240)

at org.apache.sling.i18n.impl.JcrResourceBundleProvider.onChange(JcrResourceBundleProvider.j ava:220)

at org.apache.sling.resourceresolver.impl.observation.BasicObservationReporter.reportChanges (BasicObservationReporter.java:211)

at org.apache.sling.resourceresolver.impl.observation.BasicObservationReporter.reportChanges (BasicObservationReporter.java:189)

at org.apache.sling.resourceresolver.impl.providers.ResourceProviderTracker.postResourceProviderChange(ResourceProviderTracker.java:371)

at org.apache.sling.resourceresolver.impl.providers.ResourceProviderTracker.access$400(Resou rceProviderTracker.java:59)

at org.apache.sling.resourceresolver.impl.providers.ResourceProviderTracker$2.run(ResourcePr oviderTracker.java:478)

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

For me it does not seem that your code is involved here. It's all Sling code, Oak code or product code. Please report this to Adobe support.

Show previous replies

V

vasudevaraog731

Level 3

Hi Sreenu,

Please confirm if the issue got fixed.The Same Waring present in AEM 6.3.1.0 .The log size increasing drastically and repeating multiple times in day(While we are verifying the log it's repeated(200-300) times) with session has been idle for 1,2,3,4 minutes like this throwing Waring exception

Translate

sreenu539Author

Level 7

Please look at the Jorg Hoh comment above regarding

[1] [SLING-7313] ResourceResolverImpl#refresh should also refresh the internal resourceTyperesourceResolver - ASF JIRA

Translate

Sign up

Login with SSO

Login to the community

Login with SSO