DengQin opened a new issue, #33339:
URL: https://github.com/apache/shardingsphere/issues/33339

   ## Question
   .278277293+08:00
   ### Cause: java.sql.SQLException: Unknown exception: Cannot invoke method 
hashCode() on null object
   2024-10-21T18:52:20.278289903+08:00
   ; uncategorized SQLException; SQL state [HY000]; error code [30000]; Unknown 
exception: Cannot invoke method hashCode() on null object; nested exception is 
java.sql.SQLException: Unknown exception: Cannot invoke method hashCode() on 
null object
   2024-10-21T18:52:20.278305818+08:00
        at 
org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:89)
 ~[spring-jdbc-5.2.6.RELEASE.jar:5.2.6.RELEASE]
   2024-10-21T18:52:20.278318225+08:00
        at 
org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81)
 ~[spring-jdbc-5.2.6.RELEASE.jar:5.2.6.RELEASE]
   2024-10-21T18:52:20.278330711+08:00
        at 
org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:81)
 ~[spring-jdbc-5.2.6.RELEASE.jar:5.2.6.RELEASE]
   2024-10-21T18:52:20.278339694+08:00
        at 
org.mybatis.spring.MyBatisExceptionTranslator.translateExceptionIfPossible(MyBatisExceptionTranslator.java:88)
 ~[mybatis-spring-2.0.5.jar:2.0.5]
   2024-10-21T18:52:20.278352522+08:00
        at 
org.mybatis.spring.SqlSessionTemplate$SqlSessionInterceptor.invoke(SqlSessionTemplate.java:440)
 ~[mybatis-spring-2.0.5.jar:2.0.5]
   2024-10-21T18:52:20.278360916+08:00
        at com.sun.proxy.$Proxy141.selectList(Unknown Source) ~[?:?]
   2024-10-21T18:52:20.278372966+08:00
        at 
org.mybatis.spring.SqlSessionTemplate.selectList(SqlSessionTemplate.java:223) 
~[mybatis-spring-2.0.5.jar:2.0.5]
   


-- 
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]

Reply via email to