You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cocoon.apache.org by bu...@apache.org on 2002/08/29 20:41:42 UTC

DO NOT REPLY [Bug 12173] New: - SQLTransformer Query object prematurely closes connection causing NullPointerException when accessing ResultSet

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12173>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12173

SQLTransformer Query object prematurely closes connection causing NullPointerException when accessing ResultSet

           Summary: SQLTransformer Query object prematurely closes
                    connection causing NullPointerException when accessing
                    ResultSet
           Product: Cocoon 2
           Version: 2.0.3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: sitemap components
        AssignedTo: cocoon-dev@xml.apache.org
        ReportedBy: johnsbrn@hotmail.com


The Query.execute() method closes the connection object after storing the ResultSet  and ResultSetMetaData objects. This causes a NullPointerException when retrieving results from certain J2EE connections (FirebirdDS, possibly others). There is no reason for the conn.close() call as Query.close() closes everything and is called at the end of the SQLTransformer.executeQuery() method. Removing conn.close() and conn = null from the end of the Query.excute() method fixes the problem.

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org