DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30729>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30729 Connection not released in SQL extension Summary: Connection not released in SQL extension Product: XalanJ2 Version: 2.6 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Major Priority: Other Component: org.apache.xalan.lib.sql AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I use some xsl doing a lot of queries in an Oracle Database 8.1.7 (classes12.zip). My problem is that the transformation process creates a new connection for each query. This can failed the process if it's reached the maximum number of connections allowed by the database provider. I noticed that org.apache.xalan.lib.sql.SQLDocument.executeSQLStatement() never relases the connection after the execution of a statement. So each time, the process enter this function, a new connection is created by the ConnectionPool. I added a line at the end of this function to relase the connection. > private void executeSQLStatement() throws SQLException > [...] > > m_ResultSet = m_Statement.getResultSet(); + m_ConnectionPool.releaseConnection(conn); > } > My problem seems to be solved. Now, only one connection is created by the process. PS: first time I post a bug, let me know if you need more information. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
