Sling mapping issue in Production Publish 2

[sivaramr5911311]

There was an issue with short url mapping in Production Publish 2 instance for one of our site where we had the mapping under /etc/map/https/www.xyz.com. The short URL was resolving in Prod publish 1 instance whereas it was not resolving in Publish 2.

Due to this, when the pages are accessed pages from the site, 404 page not found was coming up occasionally (whenever the request hits dispatcher 2 which points to publish 2). We tried the following steps to resolve the issue. Package /etc/map/https/www.xyz.com and /etc/map/http/www.xyz.com from Publish 1 and installed it in Publish 2 – Issue was not resolved. We restarted the following 2 bundles – The issue was resolved. Apache Sling JCR Resource Resolver org.apache.sling.jcr.resource Apache Sling Resource Resolver org.apache.sling.resourceresolver The issue was resolved but we are unable to determine the root cause of this issue. So that we could prevent this kind of issue from occurring again in production environment.

Any idea what could have caused this issue?

[vanegi]

Please confirm if you have log in as an admin via CRXDE and then do the same request again to validate this. Also check if the mapping is actually applied by AEM:

- Go to http://<host>:<port>/system/console/jcrresolver

- Under "Mapping Map Entries", check if the entries are appearing there.

You can also setup a DEBUG logger on "org.apache.sling.resourceresolver" to check how the resolution is happening and which resource resolver settings are being applied.

[Hamid1350]

Do you have any rewrite rules defined at httpd server level ?

[ChitraMadan · Accepted solution]

Hi @sivaramr5911311 ,

I have faced this issue quite often, whenever we make a change in sling mappings, we mostly have to restart the bundle, as you mentioned.

One of the reason I could relate is mentioned in this article -  

https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html#rebuil...

Although, it mentions that Sling automatically builds the filter, but looks like when we do a restart of the bundle, this filter gets build again.

[bhagchand]

Hi @sivaramr5911311 

Can you please assist how we restart these bundles "We restarted the following 2 bundles – The issue was resolved. Apache Sling JCR Resource Resolver org.apache.sling.jcr.resource Apache Sling Resource Resolver org.apache.sling.resourceresolver "

Because we are getting same issue on our production environment

Currently we are using AEM as CS

Thanks in advance

[pcheedel1]

After i have done this my AEM instance is throwing 503 authentication service and not able to access crx or bundles or logs even if i give correct credentials can you please help here