AEM looking for a valid user on content pages

Forum|Forum|6 years ago
November 26, 2019
9 replies
8851 views

I just upgraded to AEM 6.5.2 and have content copied from production. The number of users available on different level servers will NOT be same, different levels have different set of users.

Now when I load a page by navigation from coral UI in column view and load any page, the error log is full of missing user errors:

GET /mnt/overlay/wcm/core/content/sites/jcr:content/views/column.0.40.html/content/abc/global/en_yy HTTP/1.1] WARN AEM Unable to get display name for USER

javax.jcr.RepositoryException: Unable to retrieve properties for USER

at com.adobe.granite.security.user.internal.UserPropertiesManagerImpl.checkValidAuthorizableInfo(UserPropertiesManagerImpl.java:676)

The USER value here is user-id for different user, who might have created of modified the page. I believe AEM is trying to read from page version history or something.

As the pages are copy of production, but users are not available on every level, I see 100s of such errors on each level.

If I add these missing users on test levels the error goes away, but this seems an un-necessary task for test levels or even on local. [ I will NOT want to copy all users if I just need the content.]

I tried to look for this issue and it seems that people have reported this as known AEM issue.

Migration Error while upgrading to AEM 6.2 from 6.4

If anyone has encountered OR resolved this issue, please suggest.

Thanks in Advance!!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by vish.dhaliwal

Hello,

This is a known issue with internal JIRA ID GRANITE-26948 which has been resolved in current master branch.

The workaround is to redirect the warnings into another logs with level "Error".

Regards,

Vishu

V

vish.dhaliwal

Accepted solution

Adobe Employee

Hello,

This is a known issue with internal JIRA ID GRANITE-26948 which has been resolved in current master branch.

The workaround is to redirect the warnings into another logs with level "Error".

Regards,

Vishu

sawan051Author

Level 3

Thanks for quick response Vish.dhaliwal .

Will this fix be available in any upcoming hotfix or next SP?

V

vish.dhaliwal

Adobe Employee

Hey Sawan,

This might not get backported to 6.5 since there is no functional impact as such. Please raise a daycare ticket with a strong business impact statement in case you require a fix 6.5.

Regards,

Vishu

Martin-Nekula

Level 2

Hello Vishu,

this has been a problem for us as well, after the update. Could you please elaborate about how to redirect the warnings? I haven´t been able to find a configuration for this.

Best Regards

Martin