zrlw opened a new pull request, #15272:
URL: https://github.com/apache/dubbo/pull/15272

   ## What is the purpose of the change?
   there are no exception log information when Netty server or client occurs 
exception, for example, NettyHandler#exceptionCaught catched server exception 
but does not log any exception information, only disconnected info was logged:
   ```
   3.3.4-SNAPSHOT, current host: 10.1.0.250
   12:21:36.654 |-INFO  [New I/O server worker #3-5] 
bo.remoting.transport.netty.NettyHandler:82  -|  [DUBBO] The connection between 
/10.1.0.250:33222 and /10.1.0.250:36882 is established, dubbo version: 
3.3.4-SNAPSHOT, current host: 10.1.0.250
   12:21:36.655 |-INFO  [New I/O client worker #1-2] 
bo.remoting.transport.netty.NettyHandler:82  -|  [DUBBO] The connection between 
/10.1.0.250:36882 and /10.1.0.250:33222 is established, dubbo version: 
3.3.4-SNAPSHOT, current host: 10.1.0.250
   .... .... <=== Netty server encountered error,  the exception was caught by 
NettyHandler but doesn't be logged.
   12:21:36.655 |-INFO  [New I/O server worker #3-5] 
bo.remoting.transport.netty.NettyHandler:99  -|  [DUBBO] The connection between 
/10.1.0.250:33222 and /10.1.0.250:36882 is disconnected, dubbo version: 
3.3.4-SNAPSHOT, current host: 10.1.0.250
   ```
   
   ## Checklist
   - [x] Make sure there is a 
[GitHub_issue](https://github.com/apache/dubbo/issues) field for the change.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Write necessary unit-test to verify your logic correction. If the new 
feature or significant change is committed, please remember to add sample in 
[dubbo samples](https://github.com/apache/dubbo-samples) project.
   - [x] Make sure gitHub actions can pass. [Why the workflow is failing and 
how to fix it?](../CONTRIBUTING.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to