[jira] Issue Comment Edited: (IBATIS-535) iBatis not closing JDBC statements

["Kai Grabfelder (JIRA)" <ib...@incubator.apache.org>]

    [ https://issues.apache.org/jira/browse/IBATIS-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628212#action_12628212 ] 

kaig edited comment on IBATIS-535 at 9/3/08 5:21 PM:
---------------------------------------------------------------

This does not necessarily mean that iBATIS is doing something wrong. This also tends to happen when JBoss does not know that a connection has already been properly closed by spring (depending on how transaction management is configured in your application context). I had similar errors in our JBoss logs. So I think this is rather a configuration issue with the combination of JBoss, Spring and Arjuna (e.g. JBoss transactions) . Could you post more details about your configuration (application context transaction manager setup, Datasource configuration, JBoss transaction manager setup)?

      was (Author: kaig):
    This does not necessarily mean that iBATIS is doing something wrong. This also tends to happen when JBoss does not know that a connection has already been properly closed by spring (depending on how transaction management is configured in your application context). I had similar errors in our JBoss logs. So before this can be considered a bug in iBATIS I guess you should post more details about your configuration (application context transaction manager setup, Datasource configuration, JBoss transaction manager setup). 
  
> iBatis not closing JDBC statements
> ----------------------------------
>
>                 Key: IBATIS-535
>                 URL: https://issues.apache.org/jira/browse/IBATIS-535
>             Project: iBatis for Java
>          Issue Type: Bug
>          Components: SQL Maps
>    Affects Versions: 2.3.2, 2.3.3
>         Environment: Windows XP, Windows 2003, JBoss 4.0.5GA, Java 6.x, Spring 2.5.5
>            Reporter: Doug Rothauser
>
> JDBC statements aren't being closed until the Connection is closed.  
> 18:11:57,182 WARN  [WrappedConnection] Closing a statement you left open, please do your own housekeeping
> java.lang.Throwable: STACKTRACE
> 	at org.jboss.resource.adapter.jdbc.WrappedConnection.registerStatement(WrappedConnection.java:576)
> 	at org.jboss.resource.adapter.jdbc.WrappedStatement.<init>(WrappedStatement.java:62)
> 	at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.<init>(WrappedPreparedStatement.java:56)
> 	at org.jboss.resource.adapter.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:187)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy$TransactionAwareInvocationHandler.invoke(TransactionAwareDataSourceProxy.java:225)
> 	at $Proxy66.prepareStatement(Unknown Source)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at com.ibatis.common.jdbc.logging.ConnectionLogProxy.invoke(ConnectionLogProxy.java:53)
> 	at $Proxy67.prepareStatement(Unknown Source)
> 	at com.ibatis.sqlmap.engine.execution.SqlExecutor.prepareStatement(SqlExecutor.java:497)
> 	at com.ibatis.sqlmap.engine.execution.SqlExecutor.executeQuery(SqlExecutor.java:175)
> 	at com.ibatis.sqlmap.engine.mapping.statement.MappedStatement.sqlExecuteQuery(MappedStatement.java:221)
> 	at com.ibatis.sqlmap.engine.mapping.statement.MappedStatement.executeQueryWithCallback(MappedStatement.java:189)
> 	at com.ibatis.sqlmap.engine.mapping.statement.MappedStatement.executeQueryForObject(MappedStatement.java:120)
> 	at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForObject(SqlMapExecutorDelegate.java:518)
> 	at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForObject(SqlMapExecutorDelegate.java:493)
> 	at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.queryForObject(SqlMapSessionImpl.java:106)
> 	at org.springframework.orm.ibatis.SqlMapClientTemplate$1.doInSqlMapClient(SqlMapClientTemplate.java:273)
> 	at org.springframework.orm.ibatis.SqlMapClientTemplate.execute(SqlMapClientTemplate.java:209)
> 	at org.springframework.orm.ibatis.SqlMapClientTemplate.queryForObject(SqlMapClientTemplate.java:271)
> 	at com.fcci.surveyrequest.dao.SurveyRequestSourceDAOImpl.getPhid(SurveyRequestSourceDAOImpl.java:80)
> 	at com.fcci.surveyrequest.dao.SurveyRequestSourceDAOImpl.getSurveyRequest(SurveyRequestSourceDAOImpl.java:151)
> 	at com.fcci.ra.RaServlet.acountDetails(RaServlet.java:1268)
> 	at com.fcci.ra.RaServlet.doAction(RaServlet.java:322)
> 	at com.fcci.expresswrite.EwServlet.handleRequest(EwServlet.java:640)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.