Getting too many warning logs of emulator in publisher instance for every request impacting publisher and sometimes bringing it down. | Community
Skip to main content
D
Adobe Champion
deepak3344Adobe Champion
Adobe Champion
January 23, 2018
Solved

Getting too many warning logs of emulator in publisher instance for every request impacting publisher and sometimes bringing it down.

  • January 23, 2018
  • 3 replies
  • 1931 views

Hi All,

Currently, in our Prod publishers, we are facing a large number of warning logs for every request which is impacting our publishers heavily.

Example, WARN [19.107.65.92 [1516214634238] GET HTTP/1.1] com.day.cq.wcm.mobile.api.device.DeviceGroup getEmulator: skipping emulator [/libs/wcm/mobile/components/emulators/w800], resource doesn't exist.

There is one related thread to it Publish Instance has many Warnings in Log about Emulator where this issue is suggested as Adobe bug and mentioned current workaround is to add a useradmin rule on the publish instances to allow the user group 'everyone' to read /lib/wcm/mobile/components/emulators/ using the /useradmin console.

I want to understand why we getting these mobile simulator issues as we are not using or referencing in the code.

Help and inputs on the root cause/reason for getting these errors will be grateful.

Regards

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 smacdonald2008

Confirmed - our team said: "To fix you need allow the user group 'everyone' to READ for (/lib/wcm/mobile/components/emulators)"

3 replies

smacdonald2008
smacdonald2008
Level 10
January 23, 2018

Did you try the workaround in that other thread.   

smacdonald2008
smacdonald2008
Level 10
January 23, 2018

I am also checking internally to see if this is a known issue.

smacdonald2008
smacdonald2008Accepted solution
Level 10
January 23, 2018

Confirmed - our team said: "To fix you need allow the user group 'everyone' to READ for (/lib/wcm/mobile/components/emulators)"

    Terms & ConditionsAccessibility statement

    Loading footer...