Unclosed ResourceResolver was created at LivefyreRightsRequestPoller

[venkateswarm326]

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)

[Jörg_Hoh]

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

[venkateswarm326]

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.

[Jörg_Hoh]

The OSGI ResourceResolverFactory configuration contains a configuration if this situation needs to be logged. This was enabled in the past, but in newer AEM versions the default has been changed. So on any freshly setup instance this cannot be observed (anymore). From a personal perspective this is unfortunate

[venkateswarm326]

Hi Jörg_Hoh, Thanks for the info. Yes. The Resource resolver unclosed log is enabled in environments. And, one more issue we are facing is that occurring below exception some times in environments and it leads to server restart. Do you already have any clue on this?

[Jörg_Hoh]

Hi, I am not sure which "below exception" you are referring to, I don't see any.

[tim_funk]

I'm still observing this behavior in publisher 6.5.8

[Jörg_Hoh]

Hi Tim,

A number of fixes went into SP10 which address this area of problem. Not sure if we fixed all already.

[tim_funk]

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

[Jörg_Hoh · Accepted solution]

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.

[Aziz_ZOUAOUI_514]

Yes there is a way, here is a screenshot.

add the property enable to false on:

/etc/importers/polling/livefyre-poller/jcr:content

Hope this helps

[Bavo1]

One remark, it should be enabled. Or you can just remove the complete config of course.

[papenaarun]

Hi,

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