seata 启动日志问题

- [ ] I have searched the [issues](https://github.com/seata/seata/issues) of this repository and believe that this is not a duplicate.

### Ⅰ. Issue Description
我注册中心用consul，配置中心用apollo

查看启动日志，有如下问题需要帮助确认：
1. 10:48:07.454 ERROR --- [tyServerNIOWorker_1_13_16] i.s.core.rpc.netty.v1.ProtocolV1Decoder : Decode frame error, cause: Adjusted frame length exceeds 8388608: 539976035 - discarded

这个ERROR该如何才能让他消失？SEATA SERVER刚启动，还没有SEATA客户端连接上来。

2. 10:48:04.352 INFO --- [ttyServerNIOWorker_1_8_16] i.s.c.r.n.AbstractNettyRemotingServer : 10.132.102.146:58874 to server channel inactive.

不断有 server channel inactive.的信息打印在控制台上面，而且还有不同的IP和端口号10.132.102.156:33748，10.132.102.146:58868。我的application.yml里面没有配置这些端口。请问怎样修改才能停止这些信息的输出？

日志和配置文件见附件

### Ⅱ. Describe what happened

If there is an exception, please attach the exception trace:

[log&conf.zip](https://github.com/seata/seata/files/11035809/log.conf.zip)

### Ⅲ. Describe what you expected to happen

### Ⅳ. How to reproduce it (as minimally and precisely as possible)

1. xxx
4. xxx
5. xxx

### Ⅴ. Anything else we need to know?

### Ⅵ. Environment:

- JDK version : 1.8
- Seata version: 1.6.1
- OS :
- Others:

Start by reviewing the attached log.conf.zip and the reported Seata Server 1.6.1 startup logs and configuration. Trace the ProtocolV1Decoder and AbstractNettyRemotingServer messages to determine why the connections are rejected or become inactive. Done means the cause is reproduced or explained and a verified configuration or behavior change is documented.

Written by the indexing model from the issue text.