この会話は、活動がないためロックされています。新しい投稿を作成してください。
この会話は、活動がないためロックされています。新しい投稿を作成してください。
We keep seeing this error on Publish instance, but not on the Author instance
AEM 6.5.4. running on a Windows 2016 DataCentre OS
15.05.2020 08:57:29.199 *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.
15.05.2020 08:57:29.199 *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:419) [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.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
15.05.2020 08:57:29.200 *INFO* [Apache Sling Resource Resolver Finalizer Thread] com.adobe.granite.repository Service [8099, [org.apache.jackrabbit.oak.api.jmx.SessionMBean]] ServiceEvent UNREGISTERING
15.05.2020 08:57:29.203 *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.
15.05.2020 08:57:29.203 *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 the moment the issue is still unresolved. As it not affect any operation we ignore it, but it is still pending a resolution.
表示
返信
いいね!の合計
表示
返信
いいね!の合計
At the moment the issue is still unresolved. As it not affect any operation we ignore it, but it is still pending a resolution.
表示
返信
いいね!の合計
表示
返信
いいね!の合計
表示
返信
いいね!の合計
Hello @Eric_Stricker
I am also getting this log in error.log file. Did you find any resolution on this or check on this with Adobe support team?
Thanks!
Rashid
表示
返信
いいね!の合計
We just added a log entry to the osgi to not log it so it didn't fill the log.
OFF | false | ./logs/error.log | org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl |
表示
返信
いいね!の合計
Any solution on this. we are also facing same issue and leads to server restart every time.
表示
返信
いいね!の合計
表示
返信
いいね!の合計
Hi venkateswarm326,
Adobe support stated that this is a known issue. They suggested to create a log file to capture the information thrown by this stack trace.
Although, I didn't experience server issues (plus the stracktrace is an INFO entry). If you are experiencing server restart issues it might be caused by something else.
What AEM version are you using?
表示
返信
いいね!の合計
Hi caraujo_ec, We are using AEM 6.5 version but this issue occuring in Dev and Qual environments not in our local.
表示
返信
いいね!の合計
We are still facing this issue, are there any progress for that?
表示
返信
いいね!の合計