Sorry for the duplicate.

That's what we're doing. We're opening them for a specific bit of work and then closing them when done. The use case here is that we have this tag library that interrogates links and determines if they're a web page in the system. If they are it formats them a specific way. What this means, though, ...

That's what we're doing. We're opening them for a specific bit of work and then closing them when done.

We're closing them. And we're using the getResourceResolver() method to retrieve them.

We're closing resources correctly. What jumped out at me when I looked at our codebase in JProfiler was how long it took to even open a resourceResolver, regardless of the fact that we're closing it correctly. And we open hundreds of them per request. That's why I was curious about the overhead of e...

I inherited code for an application that uses resourceResolver instances quite liberally. Notably this code has a custom tag library for generating anchor tags. When called it takes the link and checks to see if it’s a page in the AEM using a resourceResolver. In the case of the navigation or footer...

Anything else to help troubleshoot this? I did everything you said (which I believe comes from the article I originally cited). Here's what I see for Brightcove Connector. Importing Bundlescom.ourcompany (591)That's the end of the line on this scenario, right? And yet as a test I removed Brightcove ...

Right. And this isn't what's happening with our setup. The only bundle importing either of the custom bundles is that one of them imports the other. No out of the box bundles import either custom bundle.

Nothing has worked so far. We're still stuck here.     

Jörg,Is that something you're getting from the MANIFEST file? That we're embedding core components? The bundle-plugin configuration for our project looks like this. ----            <plugin>                <groupId>org.apache.felix</groupId>                <artifactId>maven-bundle-plugin</artifactId>...