[ http://issues.apache.org/jira/browse/XALANJ-1925?page=all ]
Brian Minchau updated XALANJ-1925:
----------------------------------
Fix Version: 2.7
> Connection not released in SQL extension
> ----------------------------------------
>
> Key: XALANJ-1925
> URL: http://issues.apache.org/jira/browse/XALANJ-1925
> Project: XalanJ2
> Type: Bug
> Components: Xalan-extensions-(SQL)
> Versions: 2.6
> Environment: Operating System: Windows NT/2K
> Platform: PC
> Reporter: Didier Moraine
> Assignee: Xalan Developers Mailing List
> Fix For: 2.7
>
> 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.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
