Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Publishers intermittantly becoming unresponsive after applying service pack 6.5.7

Yonit
Level 2
Level 2

Hi.  

I am having issues with some publishers after installing service pack 6.5.7.  The author instances appear to be ok.  I am seeing this repeatedly in the log . 

13.01.2021 03:33:08.391 *INFO* [10.170.16.11 [1610530388389] GET /mnt/overlay/granite/ui/content/shell/header/actions/pulse.data.json HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Resource /mnt/overlay/granite/ui/content/shell/header/actions/pulse.data.json not found

 

Any ideas of what might be causing this?

Thanks

Yonit

 

 

6.5.7 aem-service-pack 6.5.7
1 Accepted Solution
SureshDhulipudi
Correct answer by
Community Advisor
Community Advisor
9 Replies
Yonit
Level 2
Level 2
So, I also noticed that this url is not found when not logged in as admin..., so some security setting maybe changed and now it can't do what it needs to do? When logged in as admin, I can hit this url, but I don't know what's trying to hit it in the log - just an observation.
neilwebbcbs
Level 1
Level 1

I saw a couple of my 6.5.7 publish instances hang up recently, with what Adobe support have attributed to a possible deadock in the service registry.
Have a look in your thread dumps and see if you have any blocked threads as per: https://issues.apache.org/jira/browse/FELIX-6252

I'm told that this issue is resolved in 6.5.8.

Yonit
Level 2
Level 2
"149.128.11.129 [1610664185673] HEAD /en_us.html HTTP/1.1" #1734 prio=5 os_prio=0 tid=0x00007f95540e2800 nid=0x2b5358 waiting for monitor entry [0x00007f952f1e1000] java.lang.Thread.State: BLOCKED (on object monitor) at org.apache.felix.scr.impl.ComponentRegistry.updateChangeCount(ComponentRegistry.java:722) - waiting to lock <0x00000006c0356120> (a java.lang.Object) at org.apache.felix.scr.impl.BundleComponentActivator.updateChangeCount(BundleComponentActivator.java:778) at org.apache.felix.scr.impl.manager.AbstractComponentManager.setState(AbstractComponentManager.java:1420) at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:962) at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:900) at org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:348) at org.apache.felix.framework.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:248) at org.apache.felix.framework.ServiceRegistry.getService(ServiceRegistry.java:350)
Yonit
Level 2
Level 2
Did anyone mention when there will be 6.5.8? Is there anything I can do for this publisher? I can restart it, but it never lasts a full day.
Monsieurcreosote
Level 1
Level 1

Hi Yonit. Adobe support have advised, that 6.5.8 is scheduled for 25th February.

There is another thread on the topic, regarding an available hotfix
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-5-upgrade-to-6-5-7-c...

SureshDhulipudi
Correct answer by
Community Advisor
Community Advisor