[ http://issues.apache.org/jira/browse/IBATIS-266?page=comments#action_12367244 ]
Sven Boden commented on IBATIS-266: ----------------------------------- Can you attach the errors you get from iBatis (the complete stacktrace) to the JIRA. Other points: 1) It's pretty exceptional doing commits or rollbacks in stored procedures as it limits the reusability of your stored procedures. 2) The problem you're seeing is probably a DB2 driver problem. When DB2 does a rollback it also closes all ResultSets in the same unit of work (a commit e.g. will not). I vaguely remember a trick in DB2 using 2 Connections to get work done without DB2 bailing out, but that's not going make it in iBATIS. 3) Are you handling the exception possibly returned from the call to the stored procedure? > when a roll back occurs in stored procedure. The status is not being handled > by IBATIS causing it to crash. > ------------------------------------------------------------------------------------------------------------ > > Key: IBATIS-266 > URL: http://issues.apache.org/jira/browse/IBATIS-266 > Project: iBatis for Java > Type: Bug > Versions: 2.1.5 > Environment: Websphere Studio Application Developer running on Windows XP . > Stored procedure being called is in DB2. > Reporter: Mohamed Asad > > IBATIS does not handle SP Status returned back from the Stored procedure when > a roll back is occured > The rollback command is in the StoredProcedure and not in the Java Code. > When the Stored procedure > is rolled back in DB2 . The iBATIS code just crashes. > I tried calling the Same SP from websphere tool and it did recieve a > SPStatus. -- 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
