wsm12138 opened a new issue, #20713: URL: https://github.com/apache/shardingsphere/issues/20713
## Bug Report ### Which version of ShardingSphere did you use? 97bc2168039c09728fc8c651c82ee9bddf641fef ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? ShardingSphere-Proxy ### Expected behavior have error but connection still connect ### Actual behavior have error but connection interrupt  ### Reason analyze (If you can) ``` [INFO ] 2022-09-01 08:36:22.124 [ShardingSphere-Command-94] ShardingSphere-SQL - Actual SQL: ds_0 ::: SELECT c AS c FROM sbtest5 WHERE id=? /*shadow:true*/ ::: [18088786] [ERROR] 2022-09-01 08:36:22.125 [ShardingSphere-Command-98] o.a.s.p.f.c.CommandExecutorTask - Exception occur: java.lang.IllegalArgumentException: Illegal base64 character 2d at java.base/java.util.Base64$Decoder.decode0(Base64.java:847) at java.base/java.util.Base64$Decoder.decode(Base64.java:566) at java.base/java.util.Base64$Decoder.decode(Base64.java:589) at org.apache.shardingsphere.encrypt.algorithm.AESEncryptAlgorithm.decrypt(AESEncryptAlgorithm.java:77) at org.apache.shardingsphere.encrypt.algorithm.AESEncryptAlgorithm.decrypt(AESEncryptAlgorithm.java:41) at org.apache.shardingsphere.encrypt.merge.dql.EncryptMergedResult.getValue(EncryptMergedResult.java:57) at org.apache.shardingsphere.proxy.backend.communication.DatabaseCommunicationEngine.getQueryResponseRow(DatabaseCommunicationEngine.java:213) at org.apache.shardingsphere.proxy.frontend.mysql.command.query.binary.execute.MySQLComStmtExecuteExecutor.getQueryRowPacket(MySQLComStmtExecuteExecutor.java:145) at org.apache.shardingsphere.proxy.frontend.mysql.command.query.binary.execute.MySQLComStmtExecuteExecutor.getQueryRowPacket(MySQLComStmtExecuteExecutor.java:70) at org.apache.shardingsphere.proxy.frontend.mysql.command.MySQLCommandExecuteEngine.writeQueryData(MySQLCommandExecuteEngine.java:90) at org.apache.shardingsphere.proxy.frontend.command.CommandExecutorTask.executeCommand(CommandExecutorTask.java:113) at org.apache.shardingsphere.proxy.frontend.command.CommandExecutorTask.run(CommandExecutorTask.java:77) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:833) ``` ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. 1. start proxy 2. config proxy `CREATE ENCRYPT RULE sbtest1 ( COLUMNS( (NAME=c,CIPHER=c,TYPE(NAME=AES,PROPERTIES('aes-key-value'='123456abc'))) ));` 3. start MySQL 4. use sysbench prepare data to MySQL,without proxy 5. use proxy execute `select ` ### Example codes for reproduce this issue (such as a github link). -- 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]
