flzxsqcysyhljt commented on issue #4471: Can ado.net connect sharding-proxy? URL: https://github.com/apache/incubator-shardingsphere/issues/4471#issuecomment-591762626 @kimmking psql connect sharding-proxy is allright. ado connect sharding-proxy: 【ado Exception】:“Received unexpected backend message CompletedResponse. Please file a bug.” 【sharding-proxy】：none navicat connect sharding-proxy: sharding-sphere-4-proxy | [INFO ] 03:15:59.533 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc01bccb9, L:/0.0.0.0:3308] READ: [id: 0xf95a48dc, L:/192.168.0.3:3308 - R:/172.16.219.142:53464] sharding-sphere-4-proxy | [INFO ] 03:15:59.534 [epollEventLoopGroup-2-1] i.n.handler.logging.LoggingHandler - [id: 0xc01bccb9, L:/0.0.0.0:3308] READ COMPLETE sharding-sphere-4-proxy | [WARN ] 03:16:00.094 [ShardingSphere-0] c.zaxxer.hikari.pool.ProxyConnection - HikariPool-2 - Connection org.postgresql.jdbc.PgConnection@206fb381 marked as broken because of SQLSTATE(08006), ErrorCode(0) sharding-sphere-4-proxy | org.postgresql.util.PSQLException: The server's client_encoding parameter was changed to UNICODE. The JDBC driver requires client_encoding to be UTF8 for correct operation. sharding-sphere-4-proxy | at org.postgresql.core.v3.QueryExecutorImpl.receiveParameterStatus(QueryExecutorImpl.java:2604) sharding-sphere-4-proxy | at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2219) sharding-sphere-4-proxy | at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:308) sharding-sphere-4-proxy | at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:441) sharding-sphere-4-proxy | at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:365) sharding-sphere-4-proxy | at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:307) sharding-sphere-4-proxy | at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:293) sharding-sphere-4-proxy | at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:270) sharding-sphere-4-proxy | at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:266) sharding-sphere-4-proxy | at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:1168) sharding-sphere-4-proxy | at com.zaxxer.hikari.pool.ProxyStatement.execute(ProxyStatement.java:103) sharding-sphere-4-proxy | at com.zaxxer.hikari.pool.HikariProxyStatement.execute(HikariProxyStatement.java) sharding-sphere-4-proxy | at org.apache.shardingsphere.shardingproxy.backend.communication.jdbc.wrapper.StatementExecutorWrapper.executeSQL(StatementExecutorWrapper.java:126) sharding-sphere-4-proxy | at org.apache.shardingsphere.shardingproxy.backend.communication.jdbc.execute.callback.ProxySQLExecuteCallback.executeSQL(ProxySQLExecuteCallback.java:78) sharding-sphere-4-proxy | at org.apache.shardingsphere.shardingproxy.backend.communication.jdbc.execute.callback.ProxySQLExecuteCallback.executeSQL(ProxySQLExecuteCallback.java:73) sharding-sphere-4-proxy | at org.apache.shardingsphere.shardingproxy.backend.communication.jdbc.execute.callback.ProxySQLExecuteCallback.executeSQL(ProxySQLExecuteCallback.java:45) sharding-sphere-4-proxy | at org.apache.shardingsphere.core.execute.sql.execute.SQLExecuteCallback.execute0(SQLExecuteCallback.java:79) sharding-sphere-4-proxy | at org.apache.shardingsphere.core.execute.sql.execute.SQLExecuteCallback.execute(SQLExecuteCallback.java:61) sharding-sphere-4-proxy | at org.apache.shardingsphere.core.execute.engine.ShardingExecuteEngine$1.call(ShardingExecuteEngine.java:119) sharding-sphere-4-proxy | at org.apache.shardingsphere.core.execute.engine.ShardingExecuteEngine$1.call(ShardingExecuteEngine.java:115) sharding-sphere-4-proxy | at java.util.concurrent.FutureTask.run(FutureTask.java:262) sharding-sphere-4-proxy | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) sharding-sphere-4-proxy | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) sharding-sphere-4-proxy | at java.lang.Thread.run(Thread.java:745)
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
