glon edited a comment on issue #10063:
URL:
https://github.com/apache/shardingsphere/issues/10063#issuecomment-819317629
@strongduanmu
After I changed the maxLifetimeMilliseconds in conf/config-sharding.yaml for
each dateasource from default 1800000 to 60000, the WARN log before
disappeared.
```
idleTimeoutMilliseconds: 60000
maxLifetimeMilliseconds: 60000
```
But, the problem still here.
Executing SQLs :
```mysql
root@localhost:6033 [(none)]>use sharding_db
Database changed
sharding_user@localhost:6033 [sharding_db]>select * from city;
Query OK, 0 rows affected, 25971 warnings (0.02 sec)
sharding_user@localhost:6033 [(none)]>
```
And it's debug level log, logs/stdout.log
```
[INFO ] 16:11:54.461 [epollEventLoopGroup-2-1]
i.n.handler.logging.LoggingHandler - [id: 0x14d7fc8a, L:/0.0.0.0:6033] READ:
[id: 0xbe9d76e7, L:/10.13.15.140:6033 - R:/10.13.8.18:14735]
[INFO ] 16:11:54.463 [epollEventLoopGroup-2-1]
i.n.handler.logging.LoggingHandler - [id: 0x14d7fc8a, L:/0.0.0.0:6033] READ
COMPLETE
[INFO ] 16:11:56.319 [ShardingSphere-Command-1] ShardingSphere-SQL - Logic
SQL: select * from city
[INFO ] 16:11:56.319 [ShardingSphere-Command-1] ShardingSphere-SQL -
SQLStatement:
SelectStatementContext(super=CommonSQLStatementContext(sqlStatement=org.apache.shardingsphere.sql.parser.sql.statement.dml.SelectStatement@1b38ed33,
tablesContext=org.apache.shardingsphere.sql.parser.binder.segment.table.TablesContext@2436f092),
tablesContext=org.apache.shardingsphere.sql.parser.binder.segment.table.TablesContext@2436f092,
projectionsContext=ProjectionsContext(startIndex=7, stopIndex=7,
distinctRow=false, projections=[ShorthandProjection(owner=Optional.empty,
actualColumns=[])]),
groupByContext=org.apache.shardingsphere.sql.parser.binder.segment.select.groupby.GroupByContext@90251ca,
orderByContext=org.apache.shardingsphere.sql.parser.binder.segment.select.orderby.OrderByContext@3c98a0d5,
paginationContext=org.apache.shardingsphere.sql.parser.binder.segment.select.pagination.PaginationContext@60159300,
containsSubquery=false)
[INFO ] 16:11:56.319 [ShardingSphere-Command-1] ShardingSphere-SQL - Actual
SQL: ds_0 ::: select * from city
[ERROR] 16:11:56.491 [ShardingSphere-Command-1]
o.a.s.s.f.c.CommandExecutorTask - Exception occur:
java.sql.SQLException: Operation not allowed after ResultSet closed
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:965)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:898)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:887)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:861)
at com.mysql.jdbc.ResultSetImpl.checkClosed(ResultSetImpl.java:733)
at com.mysql.jdbc.ResultSetImpl.next(ResultSetImpl.java:6279)
at
com.zaxxer.hikari.pool.HikariProxyResultSet.next(HikariProxyResultSet.java)
at
org.apache.shardingsphere.sharding.execute.sql.execute.result.StreamQueryResult.next(StreamQueryResult.java:50)
at
org.apache.shardingsphere.sharding.merge.dql.iterator.IteratorStreamMergedResult.next(IteratorStreamMergedResult.java:41)
at
org.apache.shardingsphere.shardingproxy.backend.communication.jdbc.JDBCDatabaseCommunicationEngine.next(JDBCDatabaseCommunicationEngine.java:138)
at
org.apache.shardingsphere.shardingproxy.backend.text.query.QueryBackendHandler.next(QueryBackendHandler.java:57)
at
org.apache.shardingsphere.shardingproxy.frontend.mysql.command.query.text.query.MySQLComQueryPacketExecutor.next(MySQLComQueryPacketExecutor.java:135)
at
org.apache.shardingsphere.shardingproxy.frontend.mysql.command.MySQLCommandExecuteEngine.writeQueryData(MySQLCommandExecuteEngine.java:81)
at
org.apache.shardingsphere.shardingproxy.frontend.command.CommandExecutorTask.executeCommand(CommandExecutorTask.java:101)
at
org.apache.shardingsphere.shardingproxy.frontend.command.CommandExecutorTask.run(CommandExecutorTask.java:71)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[INFO ] 16:11:56.517 [ShardingSphere-Command-2] ShardingSphere-SQL - Logic
SQL: SELECT DATABASE()
[INFO ] 16:11:56.518 [ShardingSphere-Command-2] ShardingSphere-SQL -
SQLStatement:
SelectStatementContext(super=CommonSQLStatementContext(sqlStatement=org.apache.shardingsphere.sql.parser.sql.statement.dml.SelectStatement@371321cf,
tablesContext=org.apache.shardingsphere.sql.parser.binder.segment.table.TablesContext@eed01c5),
tablesContext=org.apache.shardingsphere.sql.parser.binder.segment.table.TablesContext@eed01c5,
projectionsContext=ProjectionsContext(startIndex=7, stopIndex=16,
distinctRow=false, projections=[ExpressionProjection(expression=DATABASE(),
alias=Optional.empty)]),
groupByContext=org.apache.shardingsphere.sql.parser.binder.segment.select.groupby.GroupByContext@4faf163c,
orderByContext=org.apache.shardingsphere.sql.parser.binder.segment.select.orderby.OrderByContext@294a4694,
paginationContext=org.apache.shardingsphere.sql.parser.binder.segment.select.pagination.PaginationContext@779172b,
containsSubquery=false)
[INFO ] 16:11:56.518 [ShardingSphere-Command-2] ShardingSphere-SQL - Actual
SQL: ds_3 ::: SELECT DATABASE()
```
logback.xml :
```yaml
<configuration>
<appender name="file"
class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>sharding.log</file>
<rollingPolicy
class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>sharding.%d{yyyy-MM-dd}.log</fileNamePattern>
<maxHistory>60</maxHistory>
<!--<totalSizeCap>1GB</totalSizeCap>-->
</rollingPolicy>
<encoder>
<pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{80} -
%msg%n</pattern>
</encoder>
</appender>
<appender name="console" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>[%-5level] %d{HH:mm:ss.SSS} [%thread] %logger{36} -
%msg%n</pattern>
</encoder>
</appender>
<logger name="org.apache.shardingsphere" level="info" additivity="false">
<appender-ref ref="console"/>
<appender-ref ref="file"/>
</logger>
<root>
<level value="debug" />
<appender-ref ref="console" />
<appender-ref ref="file" />
</root>
</configuration>
```
--
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:
us...@infra.apache.org
