[ http://issues.apache.org/jira/browse/IBATIS-338?page=comments#action_12434022 ] adamb commented on IBATIS-338: ------------------------------
I have a replicable situation in development and am investigating the issue now. Preliminary work suggests taht it is not an iBATIS issue at all.... some framework in deployed mode is creating a loop in the exception hierarchy??? Can only be caused by something that uses Throwable.initCause()? > NestedSqlException stack overflow > --------------------------------- > > Key: IBATIS-338 > URL: http://issues.apache.org/jira/browse/IBATIS-338 > Project: iBatis for Java > Issue Type: Bug > Affects Versions: 2.1.5 > Reporter: adamb > > ... > at > com.ibatis.common.jdbc.exception.NestedSQLException.toString(NestedSQLException.java:113) > at > com.ibatis.common.jdbc.exception.NestedSQLException.toString(NestedSQLException.java:113) > ... > In the code you can see that if cause==this then the > NestedSqlException.toString() method will infinitely recurse causing a stack > overflow. I'm not sure what is causeing (cause==this) to be set to this > though... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
