low-latency

描述(Description)

描述你遇到了什么问题

用户点播视频，PC端使用WebRtc播放，当用户关闭视频后，云服务器利用回调函数，主动踢掉用户播放的视频流，该过程进行十几次后，云服务器的CPU一直处于98%的状态，即使没有任何推流操作，cpu也无法得到释放。

1. SRS版本(Version): v 4.0.198

重现(Replay)

重现Bug的步骤(How to replay bug?)

1. 本地推流到SRS云服务器
2. PC端成功播放视频后，主动关闭视频，云服务器使用回调函数，进行主动踢流
3. 重复十几次后，CPU处于98%的状态

期望行为(Expect)

描述你期望发生的事情(Please describe your expectation)

频繁推流、拉流、

Describe the bug

Currently keys written to server.conf go undetected.

This means that not only typos go undetected, but lack of validation is a risk during version migration as settings that used to apply in a previous version have no effect in a newer one without warning -- even if new settings are supposed to be used.

To reproduce

• Create a key with a typo.
• Watch the QuestDB

Add --add-exports jdk.management/com.ibm.lang.management.internal only when OpenJ9 detected.

Otherwise we got WARNING: package com.ibm.lang.management.internal not in jdk.management in logs

For example, given a simple pipeline such as:

Pipeline p = Pipeline.create();
p.readFrom(TestSources.items("the", "quick", "brown", "fox"))
 .aggregate(aggregator)
 .writeTo(Sinks.logger());

I'd like aggregator to be something requiring a non-serialisable dependency to do its work.

I know I can do this:

Pipeline p = Pipeline.create();
p.readFrom(TestSource