Upgrade to AEM 6.3 : Closed unclosed ResourceResolver ;Unclosed ResourceResolver was created | Community
Skip to main content
lakshmiv1629557
lakshmiv1629557
New Participant
Jun 7, 2017 6:23 PM UTC
Solved

Upgrade to AEM 6.3 : Closed unclosed ResourceResolver ;Unclosed ResourceResolver was created

Hi All,

  after upgrading from AEM 6.2 to AEM 6.3 , we upgraded uber-jar to 6.3 and seeing below issues in the logs.

Issue 1:

07.06.2017 14:00:45.009 *WARN* [Apache Sling Resource Resolver Finalizer Thread] org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl Closed unclosed ResourceResolver. The creation stacktrace is available on info log level.

07.06.2017 14:00:45.009 *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:514)

        at org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl.register(CommonResourceResolverFactoryImpl.java:217)

        at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.<init>(ResourceResolverImpl.java:101)

        at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.<init>(ResourceResolverImpl.java:94)

        at org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl.getResourceResolverInternal(CommonResourceResolverFactoryImpl.java:262)

        at org.apache.sling.resourceresolver.impl.ResourceResolverFactoryImpl.getServiceResourceResolver(ResourceResolverFactoryImpl.java:92)

        at com.day.cq.dam.s7dam.common.analytics.impl.SiteCatalystReportRunner.getResourceResolver(SiteCatalystReportRunner.java:140)

        at com.day.cq.dam.s7dam.common.analytics.impl.SiteCatalystReportRunner.cacheReport(SiteCatalystReportRunner.java:80)

        at com.day.cq.dam.s7dam.common.analytics.impl.SiteCatalystReportRunner.run(SiteCatalystReportRunner.java:70)

        at org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:118)

        at org.quartz.core.JobRunShell.run(JobRunShell.java:202)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

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

Issue 2:

07.06.2017 13:43:26.808 *ERROR* [10.242.136.235 [1496857406769] GET /content/waters/master/en/topics/food-safety/veterinary-drugs-in-food.html HTTP/1.1] com.adobe.cq.sightly.WCMUsePojo Failed to activate Use class

java.lang.NullPointerException: null

        at com.waters.aem.core.controllers.Hero.generateCTAlist(Hero.java:26)

        at com.waters.aem.core.controllers.Hero.activate(Hero.java:20)

        at com.adobe.cq.sightly.WCMUsePojo.init(WCMUsePojo.java:84)

we don't have these issues in the earlier version. Not sure what changes caused these . Any help in finding the root cause is appreciated.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Feike_Visser1
    Feike_Visser1Accepted solution
    Employee
    Jun 8, 2017 7:41 PM UTC

    In Log Support (/system/console/slinglog), you can suppress the logging.

    On top of that I would recommend you to raise a support ticket for it.

    View reply

    19 replies

    Show previous replies
    rosettar4717409
    rosettar4717409
    New Participant
    Jun 27, 2017 8:33 PM UTC

    Is there an actual resolution for this yet?  What was the result for the CQ-4210433 ticket?

    Translate
    jonnow
    jonnow
    Level 2
    Jun 13, 2017 12:48 AM UTC

    Thank you Feike for raising the ticket.

    Would be great if anyone can suggest a temporary solution (eg, disabling the SiteCatalystReportRunner) until this is resolved.

    Translate
    Feike_Visser1
    Feike_Visser1
    Employee
    Jun 12, 2017 6:10 AM UTC

    I have create an internal ticket for you, reference: CQ-4210433

    Translate
    Feike_Visser1
    Feike_Visser1
    Employee
    Jun 12, 2017 5:51 AM UTC

    Sure that is why I requested to raise a support ticket.

    Indeed my suggestion for the logging is just to hide it.

    Translate
      jonnow
      jonnow
      Level 2
      Jun 11, 2017 12:28 AM UTC

      Hi Feike, not sure why this was marked correct but suppress the log does not fix anything.

      There seems to be a potential memory leak in SiteCatalyst report runner.

      Translate
      Feike_Visser1
      Feike_Visser1Accepted solution
      Employee
      Jun 8, 2017 7:41 PM UTC

      In Log Support (/system/console/slinglog), you can suppress the logging.

      On top of that I would recommend you to raise a support ticket for it.

      Translate
      lakshmiv1629557
      lakshmiv1629557Author
      New Participant
      Jun 8, 2017 3:31 PM UTC

      Hi Visser,

           Issue at line 26 on custom code is fixed , now the only issue we see is .CommonResourceResolverFactoryImpl Unclosed ResourceResolver which is filling up the logs, how do i disable this getting logged?

      Translate
      Feike_Visser1
      Feike_Visser1
      Employee
      Jun 8, 2017 8:52 AM UTC

      On your error in the custom-code, what is at line 26 in your code?

      com.waters.aem.core.controllers.Hero.generateCTAlist(Hero.java:26)

      Translate
      felixw7930278
      New Participant
      Jun 8, 2017 7:04 AM UTC

      We have the same issue after going to 6.3. We dont use Site Catalyst or s7 (but s7 bundle is running as per default).

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...