AEM SDK local error.log 1TB in 10 minutes with ThreadLocalCleaner messages | Community
Skip to main content
T
TB3dock
Level 8
October 20, 2023
Solved

AEM SDK local error.log 1TB in 10 minutes with ThreadLocalCleaner messages

  • October 20, 2023
  • 3 replies
  • 1344 views

My local env used to work, now I get logs fill with trillions of the below messages:

Nothing has changed as far as I know (same java, same build process, same sdk)

Anyone know why ThreadLocalCleaner would be running thousands of times a second?

 

 

Any ideas whats causing this, and how I can fix?

 

20.10.2023 10:56:30.229 *DEBUG* [sling-default-4] org.apache.sling.commons.threads.impl.ThreadPoolExecutorCleaningThreadLocals Collecting changes to ThreadLocal for thread Thread[sling-default-4,5,main] from now on...

20.10.2023 10:56:30.229 *DEBUG* [sling-default-4] org.apache.sling.commons.threads.impl.ThreadLocalCleaner Thread locals: saved 16 references, size: 3, threshold: 10

20.10.2023 10:56:30.229 *DEBUG* [sling-default-4] org.apache.sling.commons.threads.impl.ThreadLocalCleaner Inheritable thread locals: saved null references

20.10.2023 10:56:30.229 *DEBUG* [ApacheSlingdefault_QuartzSchedulerThread] org.quartz.simpl.PropertySettingJobFactory Producing instance of Job 'DEFAULT.Registered Service.7139', class=org.apache.sling.commons.scheduler.impl.NonParallelQuartzJobExecutor

20.10.2023 10:56:30.229 *DEBUG* [sling-default-4] org.quartz.core.JobRunShell Calling execute on job DEFAULT.Registered Service.4862

20.10.2023 10:56:30.229 *DEBUG* [ApacheSlingdefault_QuartzSchedulerThread] org.apache.sling.commons.threads.impl.DefaultThreadPool Executing runnable:  org.quartz.core.JobRunShell@49697927, pool=default, active=1, corePoolSize=10, maxPoolSize=10, queueSize=0

20.10.2023 10:56:30.229 *DEBUG* [sling-default-4-Registered Service.4862] org.apache.sling.commons.scheduler.impl.QuartzScheduler Executing job job 'org.apache.jackrabbit.oak.jcr.observation.ChangeProcessor$4@39ce4ddf' with name 'Registered Service.4862'

20.10.2023 10:56:30.229 *DEBUG* [ApacheSlingdefault_QuartzSchedulerThread] org.quartz.core.QuartzSchedulerThread batch acquisition of 1 triggers

20.10.2023 10:56:30.229 *DEBUG* [sling-default-6] org.apache.sling.commons.threads.impl.ThreadPoolExecutorCleaningThreadLocals Collecting changes to ThreadLocal for thread Thread[sling-default-6,5,main] from now on...

20.10.2023 10:56:30.229 *DEBUG* [sling-default-6] org.apache.sling.commons.threads.impl.ThreadLocalCleaner Thread locals: saved 16 references, size: 3, threshold: 10

20.10.2023 10:56:30.229 *DEBUG* [sling-default-6] org.apache.sling.commons.threads.impl.ThreadLocalCleaner Inheritable thread locals: saved null references

20.10.2023 10:56:30.229 *DEBUG* [sling-default-4] org.apache.sling.commons.threads.impl.ThreadPoolExecutorCleaningThreadLocals Cleaning up thread locals for thread Thread[sling-default-4,5,main]...

20.10.2023 10:56:30.229 *DEBUG* [sling-default-4] org.apache.sling.commons.threads.impl.ThreadLocalCleaner Restored inheritableThreadLocals to a null value

20.10.2023 10:56:30.229 *DEBUG* [sling-default-4] org.apache.sling.commons.threads.impl.ThreadLocalCleaner Restored threadLocals with to 16 references, size 3, thresho

Best answer by joerghoh

Hi Jorg, since 3 years se use log.debug when debugging locally.  However, due to this weird issue, ive been changing debug to info. 


Then it should be sufficient to just these few loggers to INFO.

3 replies

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity Advisor
Community Advisor
October 20, 2023

Hello @tb3dock 

 

Requesting you to access configured logs from http://localhost:4502/system/console/slinglog

 

Please check is anything has an incorrect log level

Aanchal Sikka
    T
    TB3dockAuthor
    Level 8
    October 20, 2023

    I gave up trying to find what is causing this sudden unexplained log trashing, and increased the default log level to Info as a work around.

      joerghoh
      Adobe Employee
      joerghohAdobe Employee
      Adobe Employee
      October 24, 2023

      Why did you set it to DEBUG in the first place? AEM ships with a loglevel of INFO as default.

        T
        TB3dockAuthor
        Level 8
        October 25, 2023

        Hi Jorg, since 3 years se use log.debug when debugging locally.  However, due to this weird issue, ive been changing debug to info. 

          kautuk_sahni
          Community Manager
          kautuk_sahniCommunity Manager
          Community Manager
          October 26, 2023

          @tb3dock  Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

          Kautuk Sahni
          Terms & ConditionsAccessibility statement

          Loading footer...