There is no resolution at this time. The One Identity team is working on resolving this defect. Please continue to monitor release notes for information when this defect is resolved.
By integrating the timeout() option into the destination in question's configuration statement, this issue can be bypassed.
When Syslog-ng PE hangs due to logrotate and a slow destination, it will only wait the amount of time set in the timeout() value until it tries to send logs once more. Please adjust the timeout() value accordingly for the amount, in seconds, the HTTP destination should wait before reconnecting and sending logs once more.
See the latest Syslog-ng PE admin guide for more information on the timeout() option.