Ah39 edited a comment on issue #2995: version 3.1.0 may route wrong and cause memory leak when tomcat start （ A sql route wrong to 1002 table ） URL: https://github.com/apache/incubator-shardingsphere/issues/2995#issuecomment-532033685 **two datasources (ds_0,ds_1)** sharding.jdbc.config.sharding.tables.t_xxx1.actual-data-nodes=ds_0.t_xxx1_$->{0..1001} sharding.jdbc.config.sharding.tables.t_xxx1.table-strategy.inline.sharding-column=xxx1_id sharding.jdbc.config.sharding.tables.t_xxx1.table-strategy.inline.algorithm-expression=t_xxx1_$->{xxx1_id % 1001} sharding.jdbc.config.sharding.tables.t_xxx2.actual-data-nodes=ds_1.t_xxx2_$->{0..1001} sharding.jdbc.config.sharding.tables.t_xxx2.table-strategy.inline.sharding-column=xxx2_id sharding.jdbc.config.sharding.tables.t_xxx2.table-strategy.inline.algorithm-expression=t_xxx2_$->{xxx2_id % 1001} sharding.jdbc.config.sharding.tables.t_xxx3.actual-data-nodes=ds_1.t_xxx3_$->{0..1001} sharding.jdbc.config.sharding.tables.t_xxx3.table-strategy.inline.sharding-column=xxx3_no sharding.jdbc.config.sharding.tables.t_xxx3.table-strategy.inline.algorithm-expression=t_xxx3_$->{xxx3_no % 1001} sharding.jdbc.config.sharding.tables.t_xxx4.actual-data-nodes=ds_1.t_xxx4_$->{0..1001} sharding.jdbc.config.sharding.tables.t_xxx4.table-strategy.inline.sharding-column=xxx4_no sharding.jdbc.config.sharding.tables.t_xxx4.table-strategy.inline.algorithm-expression=t_xxx4_$->{xxx4_no % 1001} SQL forexample ：get by xxx2_id （select * from t_xxx2 where xxx2_id=12343432432 ) @KomachiSion **may cause by ParsingResultCache in version 3.1.0 in 4.xxx version SQLParseResultCache may also have the problem**
---------------------------------------------------------------- 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 With regards, Apache Git Services
