Stacktraces in the logs related to Sling Distribution

[oscarfarga]

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/..., 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/..., status=500, reason=

Has anyone else experienced the same?

[SantoshSai]

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.