Installed 6.5.4 SP RRD already closed Exception | Community
Skip to main content
Level 4
Mar 22, 2020 6:20 PM UTC
Solved

Installed 6.5.4 SP RRD already closed Exception

I've installed the latest SP, 6.5.4 and now see the below error littered throughout the logs. Any quick fixes to get rid of this?

22.03.2020 19:11:00.158 *ERROR* [metrics-RRD4JReporter-1-thread-1] com.codahale.metrics.ScheduledReporter Exception thrown from RRD4JReporter#report. Exception was suppressed.
java.lang.IllegalStateException: RRD already closed, cannot store this sample
at org.rrd4j.core.RrdDb.store(RrdDb.java:512) [org.apache.sling.commons.metrics-rrd4j:1.0.2]
at org.rrd4j.core.Sample.update(Sample.java:194) [org.apache.sling.commons.metrics-rrd4j:1.0.2]
at org.apache.sling.commons.metrics.rrd4j.impl.RRD4JReporter.report(RRD4JReporter.java:260) [org.apache.sling.commons.metrics-rrd4j:1.0.2]
at com.codahale.metrics.ScheduledReporter.report(ScheduledReporter.java:235) [com.adobe.granite.dropwizard.metrics:3.2.4]
at com.codahale.metrics.ScheduledReporter$1.run(ScheduledReporter.java:174) [com.adobe.granite.dropwizard.metrics:3.2.4]
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
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.
scotty64724204Accepted solution
Level 2
May 1, 2020 9:05 PM UTC

Restart your AEM instance and it should fix it

10 replies

Employee
May 21, 2022 12:01 PM UTC
Nikhil-Kumar
New Participant
Aug 15, 2020 1:37 PM UTC

Hey,

Try restarting the AEM instance and verify the changes.

Translate
Employee
Jun 12, 2020 7:37 AM UTC
Got this error after installation of SP5
Translate
scotty64724204Accepted solution
Level 2
May 1, 2020 9:05 PM UTC

Restart your AEM instance and it should fix it

Translate
Level 4
May 1, 2020 10:36 PM UTC

True, but I would like to understand why it happens periodically. It seems to fail on the same thread over and over but the metrics still get written to. I've tried restarting a couple of related bundles but that doesn't seem to help. I also noticed the thread started having issues after some nightly maintenace jobs but that could be just a coincidence.

Translate
HeavyDevy
New Participant
Apr 17, 2020 3:15 PM UTC

I have the same Issue. Did you find out how to solve this? 

Fresh AEM 6.5.0 SP4 installed via Package Share. 

Translate
Level 4
Jun 12, 2020 11:17 AM UTC
Seems once I restarted after the install, it has gone away. Odd because usually if a SP need a restart, it does it automatically.
Translate
bohdanm45202827
New Participant
Mar 23, 2020 11:08 AM UTC
Got this exception on a fresh 6.5.2.0 environment too. It spams so much in logs
Translate