DO NOT REPLY [Bug 12047] New: - validationQuery

[bu...@apache.org]

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=12047>.
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=12047

validationQuery

           Summary: validationQuery
           Product: Commons
           Version: 1.0 Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Dbcp
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: teletype@freemail.hu


Hello,

I am using Commons DBCP with Tomcat 4.0.x and accessing MSSQL 2000 database 
server with JDBC driver from Microsoft through my own constructed JNDI SPI that 
works as a DataSource factory using BasicDataSource from DBCP. 

I get SQLException (s) frequently with "Object has been closed" message when I 
set connection timeout larger than 0. (In Enterprise Manager select server >>  
Properties >> SQL Server Properties >> Connections >> Remote Server Connections 
>> Query time-out )
). Besides these, I also set the validationQuery configuration to "select 1" 
that showing up properly in the Profiler (Monitoring tool of SQL Server). This 
setting is responsible for validating the connection before it returning from 
the pool. However when I set value of query time-out to 0 this problem not 
occours.

I feel that this is a bug because after setting the validationQuery option it 
should return valid connection.

What do you think?

Bye

ps.: I'm taking care to open and close connections with try catch finally block 
so look for the bug elsewhere.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>