Unclosed ResourceResolver was created at LivefyreRightsRequestPoller | Community
Skip to main content
Level 2
October 15, 2020
Solved

Unclosed ResourceResolver was created at LivefyreRightsRequestPoller

  • October 15, 2020
  • 3 replies
  • 50246 views

Hello Team,

 

We are seeing the unclosed resource resolver issue in logs. Please suggest.

 

13.10.2020 15:33:38.690 *INFO* [Apache Sling Resource Resolver Finalizer Thread] org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl Unclosed ResourceResolver was created here:
java.lang.Exception: Opening Stacktrace
at org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl$ResolverReference.<init>(CommonResourceResolverFactoryImpl.java:540) [org.apache.sling.resourceresolver:1.6.8]
at org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl.register(CommonResourceResolverFactoryImpl.java:235) [org.apache.sling.resourceresolver:1.6.8]
at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.<init>(ResourceResolverImpl.java:104) [org.apache.sling.resourceresolver:1.6.8]
at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.<init>(ResourceResolverImpl.java:97) [org.apache.sling.resourceresolver:1.6.8]
at org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl.getResourceResolverInternal(CommonResourceResolverFactoryImpl.java:280) [org.apache.sling.resourceresolver:1.6.8]
at org.apache.sling.resourceresolver.impl.ResourceResolverFactoryImpl.getServiceResourceResolver(ResourceResolverFactoryImpl.java:89) [org.apache.sling.resourceresolver:1.6.8]
at com.adobe.cq.social.serviceusers.internal.impl.ServiceUserWrapperImpl.getServiceResourceResolver(ServiceUserWrapperImpl.java:170) [com.adobe.cq.social.cq-social-serviceusers-impl:1.5.0]
at com.adobe.social.integrations.livefyre.livefyreAssetImporter.impl.LivefyreRightsRequestPoller.getServiceResolvers(LivefyreRightsRequestPoller.java:411) [com.adobe.cq.social.cq-social-livefyre:2.2.6]
at com.adobe.social.integrations.livefyre.livefyreAssetImporter.impl.LivefyreRightsRequestPoller.importData(LivefyreRightsRequestPoller.java:132) [com.adobe.cq.social.cq-social-livefyre:2.2.6]
at com.day.cq.polling.importer.impl.PollingImporterImpl.importData(PollingImporterImpl.java:546) [com.day.cq.cq-polling-importer:5.11.4]
at com.day.cq.polling.importer.impl.PollingImporterImpl.access$000(PollingImporterImpl.java:72) [com.day.cq.cq-polling-importer:5.11.4]
at com.day.cq.polling.importer.impl.PollingImporterImpl$1.run(PollingImporterImpl.java:448) [com.day.cq.cq-polling-importer:5.11.4]
at org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:347) [org.apache.sling.commons.scheduler:2.7.2]
at org.quartz.core.JobRunShell.run(JobRunShell.java:202) [org.apache.sling.commons.scheduler:2.7.2]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)

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

Please raise this question with AEM support. On a technical it's most likely possible, but I am not sure from a support point of view.

3 replies

joerghoh
Adobe Employee
Adobe Employee
October 16, 2020

Thanks for reporting. But there is nothing you can do about it. I am currently following up on this topic internally in Adobe.

(Fortunately this does not have any negative impact on your application.)

 

Jörg

Level 2
October 20, 2020
Hi Jörg_Hoh, Thanks for your reply. I would like to inform you of additional info that we are using the AEM 6.5.5 version and it's running on the linux server using JRE version 11. But we don't see this exception in our local environment where we are running AEM 6.5 on JRE 1.8.
tim_funk
Level 3
October 19, 2021

Is there a way to disable this Poller? We don't seem to be using anything livefyre related

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
October 23, 2021

Please raise this question with AEM support. On a technical it's most likely possible, but I am not sure from a support point of view.

Level 2
November 21, 2022

Hi,

Even we are facing same issue. Do we have any solution for this?