[Bug] EventMeshTCPServer set unknown channel options

[liutaohua]

We can see these WARN logs during startup:

2021-07-19 16:22:47,008 WARN  [eventMesh-tcp-server] ServerBootstrap(AbstractBootstrap.java:452) - Unknown channel option 'TCP_NODELAY' for channel '[id: 0xbcef744f]'
2021-07-19 16:22:47,009 WARN  [eventMesh-tcp-server] ServerBootstrap(AbstractBootstrap.java:452) - Unknown channel option 'SO_KEEPALIVE' for channel '[id: 0xbcef744f]'
2021-07-19 16:22:47,010 WARN  [eventMesh-tcp-server] ServerBootstrap(AbstractBootstrap.java:452) - Unknown channel option 'SO_TIMEOUT' for channel '[id: 0xbcef744f]'
2021-07-19 16:22:47,010 WARN  [eventMesh-tcp-server] ServerBootstrap(AbstractBootstrap.java:452) - Unknown channel option 'SO_LINGER' for channel '[id: 0xbcef744f]'

These parameters need to be set to childOption. eg.:

bootstrap.group(bossGroup, ioGroup)
                    .channel(NioServerSocketChannel.class)
//                    .option(ChannelOption.TCP_NODELAY, true)
                    .childOption(ChannelOption.TCP_NODELAY, true)

[lrhkobe]

Yes，you are right. Maybe you can submit a pr to fix it.

[liutaohua]

Yes，you are right. Maybe you can submit a pr to fix it.

OK. I'll submit it when I'm free from work

[lrhkobe]

As to the 4 channel options , do you think it is necessary to change the default value in EventMesh?

[liutaohua]

As to the 4 channel options , do you think it is necessary to change the default value in EventMesh?

Frankly, I don't have a systematic understanding of logic. I can't give an accurate reply to what values these parameters are recommended to users. Or what ideas can you put forward?

If I perform better in the stress test, I will remember to give back these values.