Stacktraces in the logs related to Sling Distribution | Community
Skip to main content
oscarfarga
oscarfarga
New Member
October 2, 2025

Stacktraces in the logs related to Sling Distribution

  • October 2, 2025
  • 3 replies
  • 268 views

We are seeing from time to time the following exception in the logs of the publish instance, related to sling distribution.
We haven't configured anything specific for sling distribution, so it is working ootb.
We haven't experienced any particular issue related to this exception, but we see it often, and wonder if it's a real error or if it should be ignored.

It's logged as INFO, which is already a bit confusing.

02.10.2025 09:04:27.513 level=INFO [pool-45-thread-1] org.apache.sling.distribution.journal.impl.subscriber.Announcer Failed to send discovery message for agent publishSubscriber, Error sending POST request to url=http://content-distribution.ns-team-content-distribution.svc.cluster.local:8080/distribution/topics/discovery/sources/148472-1512067-b22574e0-501f-478a-a829-35c1c2a8acc2/types/DiscoveryMessage, status=500, reason=
org.apache.sling.distribution.journal.MessagingException: Error sending POST request to url=http://content-distribution.ns-team-content-distribution.svc.cluster.local:8080/distribution/topics/discovery/sources/148472-1512067-b22574e0-501f-478a-a829-35c1c2a8acc2/types/DiscoveryMessage, status=500, reason=

 

Has anyone else experienced the same?

3 replies

SantoshSai
Community Advisor
SantoshSaiCommunity Advisor
Community Advisor
October 2, 2025

Hi @oscarfarga,

If it’s just occasional and your replication/distribution works fine, you can safely ignore these INFO logs. They’re expected “blips.”
If it becomes frequent or starts correlating with missing/slow distribution, then open a support ticket with Adobe to check stability of the content-distribution service.

Santosh Sai
    muskaanchandwani
    Adobe Employee
    muskaanchandwaniAdobe Employee
    Adobe Employee
    October 6, 2025

    Hello @oscarfarga 
    This is a transient log message for Sling Distribution’s discovery mechanism. If you observe no functional impact, you can safely ignore it.

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      March 16, 2026

      ​@oscarfarga Following up to see if this has been resolved. If you’ve found the answer—whether through the suggestions here or through your own troubleshooting—feel free to post the solution so others can benefit. If any reply helped along the way, marking it as accepted ensures the most useful information is easy to find. Thanks for helping close the loop!

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...