This is an issue with the type and frequency of this message being logged.
This issue does not cause any functional issues, but does make it difficult to capture other pertinent log details if the frequency is high. This issue is addressed in release 8.5 RU1.