You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2022/05/05 09:39:22 UTC

[GitHub] [shardingsphere] TeslaCN commented on issue #17308: connection leak for sharding proxy

TeslaCN commented on issue #17308:
URL: https://github.com/apache/shardingsphere/issues/17308#issuecomment-1118361059

   Hi @wsg96321 
   Your server config is not the 5.x style. You may refer to:
   https://github.com/apache/shardingsphere/blob/1699736d88db8c388413229d179eeae3da705a8b/shardingsphere-proxy/shardingsphere-proxy-bootstrap/src/main/resources/conf/server.yaml#L64-L85
   
   The WARN log `An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.` usually doesn't matter.


-- 
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: notifications-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org