[jira] Commented: (DBCP-218) basicDataSource.setLoginTimeout(n) not work?

["Bill Liu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DBCP-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12495093 ] 

Bill Liu commented on DBCP-218:
-------------------------------

Thanks Phil.

We actually wanted the first scenario: the datasource to time out if there are no connections available from the pool and the max active has been reached. I did not know the default value of maxWait was -1 and did not check it. Yes I set it to be 5 seconds and it worked.

> basicDataSource.setLoginTimeout(n) not work?
> --------------------------------------------
>
>                 Key: DBCP-218
>                 URL: https://issues.apache.org/jira/browse/DBCP-218
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.1, 1.2, 1.2.1, 1.2.2
>         Environment: Windows
>            Reporter: Bill Liu
>             Fix For: 1.3
>
>
> Hi:
> We tried to set the login timeout value of the basic data source but got the exception. Is this feature (Login timeout is not supported.)? We want the connection pool not to wait forever if the database is too busy. Any ideas? Thanks.
> In the code:
> BasicDataSource bds = new BasicDataSource();
> bds.setDriverClassName("oracle.jdbc.driver.OracleDriver");
> bds.setUsername("my username");
> bds.setPassword("my password");
> bds.setUrl("jdbc:oracle:thin:@mrhost:1521:test");
> bds.setMaxActive(2);
> bds.setLoginTimeout(5);
> Result:
> Exception in thread "main" java.lang.UnsupportedOperationException: Login timeout is not supported.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org