Issue with unclosed resource resolver in OOTB scene7 Bundle

Shashi_Mulugu

MVP

14-10-2020

Hello Team,

 

We are using AEM 6.4.2 integrated with Dynamic Media. Here to fetch the URL of synced asset we are using com.day.cq.dam.s7dam.common.utils.PublishUtilsImpl.externalizeImageDeliveryAsset() by passing the resource object of the asset.

 

We are seeing the unclosed resource resolver issue in logs. Please suggest.

 

Any other way to fetch the DM published URL if not above?

 

I suspect that in "com.day.cq.dam.scene7.impl.Scene7AEMBridgeImpl" resourceresolver might not be closed after processing.

 

14.10.2020 02:20:14.950 *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.
14.10.2020 02:20:14.950 *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:521) [org.apache.sling.resourceresolver:1.5.34]
at org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl.register(CommonResourceResolverFactoryImpl.java:218) [org.apache.sling.resourceresolver:1.5.34]
at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.<init>(ResourceResolverImpl.java:101) [org.apache.sling.resourceresolver:1.5.34]
at org.apache.sling.resourceresolver.impl.ResourceResolverImpl.<init>(ResourceResolverImpl.java:94) [org.apache.sling.resourceresolver:1.5.34]
at org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl.getResourceResolverInternal(CommonResourceResolverFactoryImpl.java:263) [org.apache.sling.resourceresolver:1.5.34]
at org.apache.sling.resourceresolver.impl.ResourceResolverFactoryImpl.getServiceResourceResolver(ResourceResolverFactoryImpl.java:96) [org.apache.sling.resourceresolver:1.5.34]
at com.day.cq.dam.scene7.impl.Scene7AEMBridgeImpl.getServiceUserScopedConfigResolver(Scene7AEMBridgeImpl.java:188) [com.day.cq.dam.cq-dam-scene7:5.11.108]
at com.day.cq.dam.scene7.impl.Scene7AEMBridgeImpl.getS7configFromResource(Scene7AEMBridgeImpl.java:138) [com.day.cq.dam.cq-dam-scene7:5.11.108]
at com.day.cq.dam.scene7.impl.ImageUrlApiImpl.getImageServerDeliveryURL(ImageUrlApiImpl.java:113) [com.day.cq.dam.cq-dam-scene7:5.11.108]
at com.day.cq.dam.scene7.impl.ImageUrlApiImpl.getImageServerDeliveryURL(ImageUrlApiImpl.java:82) [com.day.cq.dam.cq-dam-scene7:5.11.108]
at com.day.cq.dam.s7dam.common.utils.PublishUtilsImpl.externalizeImageDeliveryAsset(PublishUtilsImpl.java:260) [com.day.cq.dam.cq-dam-s7dam:5.11.168]

 

@kautuk_sahni @vanegi @Jörg_Hoh @Arun_Patidar @dan_klco @hamidk92094312 

2 Comments (2 New)
2 Comments

Jörg_Hoh

Employee

14-10-2020

Hi,

 

this is a known issue (it does not have any impact on stability), and it has been fixed with 6.4.8.2.

hamidk92094312

Employee

14-10-2020

@Shashi_Mulugu 

For future reference please post questions to the appropriate section of the community. The "ideas" tab is specific for raising Request for Feature Enhancements (RFEs).