Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events
SOLVED

How to get rid of messages about Guava deprecation?

Avatar

Level 2

Hello,

 

Our error.log on the AEM Publish instances are polluted with millions of such messages:

2023-07-18 14:47:00.810 *WARN* [sling-oak-observation-15] org.apache.jackrabbit.oak.core.GuavaDeprecation use of deprecated Guava-related API - this method is going to be removed in future Oak releases - see OAK-8874 for details

 

How to get rid of them?

 

Stacktrace:

 

java.lang.Exception: call stack
	at org.apache.jackrabbit.oak.core.GuavaDeprecation.handleCall(GuavaDeprecation.java:65)
	at org.apache.jackrabbit.oak.plugins.nodetype.TypePredicate.apply(TypePredicate.java:220)
	at com.adobe.granite.auth.requirement.impl.RequirementObserver$Diff.childNodeChanged(RequirementObserver.java:125)
	at org.apache.jackrabbit.oak.segment.MapRecord.compare(MapRecord.java:517)
	at org.apache.jackrabbit.oak.segment.SegmentNodeState.compareAgainstBaseState(SegmentNodeState.java:651)
	at com.adobe.granite.auth.requirement.impl.RequirementObserver$Diff.childNodeChanged(RequirementObserver.java:160)
	at org.apache.jackrabbit.oak.segment.MapRecord$4.childNodeChanged(MapRecord.java:471)
	at org.apache.jackrabbit.oak.segment.MapRecord.compare(MapRecord.java:517)
	at org.apache.jackrabbit.oak.segment.MapRecord.compare(MapRecord.java:462)
	at org.apache.jackrabbit.oak.segment.SegmentNodeState.compareAgainstBaseState(SegmentNodeState.java:651)
	at org.apache.jackrabbit.oak.spi.commit.DiffObserver.contentChanged(DiffObserver.java:55)
	at org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:127)
	at org.apache.jackrabbit.oak.spi.commit.BackgroundObserver$1$1.call(BackgroundObserver.java:121)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	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:829)

 

 According to the source code of the class GuavaDeprecation it should be possible to change the log level of such messages to eg. "DEBUG", using a system property (see eg. https://github.com/apache/jackrabbit-oak/blob/1.22/oak-core/src/main/java/org/apache/jackrabbit/oak/...

 

private static final String TLOGLEVEL = System.getProperty(GuavaDeprecation.class + ".LOGLEVEL", DEFAULT);

 

and then ignore them with setting higher level in the logger configuration. However, adding a runtime parameters to the java command has not helped:

 

-D"class org.apache.jackrabbit.oak.core.GuavaDeprecation.LOGLEVEL=debug"

 

AEM version is 6.5.17.0.

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Until then you can set the loglevel of

org.apache.jackrabbit.oak.core.GuavaDeprecation

to "off".

View solution in original post

5 Replies

Avatar

Employee Advisor

Hi @pkalinow81 ,

 

AFAIK, this is being worked upon by engineering and should be fixed in SP18.

 

Please check the release roadmap for the timeline

https://experienceleague.adobe.com/docs/experience-manager-release-information/aem-release-updates/u... 

 

Hope that helps!

 

Regards,

Nitesh

Avatar

Level 2

Thanks for this information. We'll see if it's fixed when the SP is ready - it's scheduled on August 31, 2023.

Avatar

Correct answer by
Employee Advisor

Until then you can set the loglevel of

org.apache.jackrabbit.oak.core.GuavaDeprecation

to "off".

Avatar

Level 2

Thanks! Actually, I couldn't set the log level to "off", but with a new Apache Sling Logging Logger Configuration it is possible to set the level to "error".This seems to be enough to disable those messages.