[
https://issues.apache.org/jira/browse/DERBY-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16208913#comment-16208913
]
Satyabrata Mohanty commented on DERBY-6970:
-------------------------------------------
Hi Rick,
It seems that by default the derby is setting 5 seconds login timeout on the
data source.
Suppose i want to set the login timeout as 3 seconds (ds.setLoginTimeout(3)) ,
but it is throwing connect timed out after exact 5 seconds.
Also i tried by setting different the login timed out like 7 seconds,10
seconds,2 seconds, 8 seconds, 15 seconds , But every time it is considering
only 5 seconds and it is throwing timed out exception only after 5 seconds that
means the configured time out property value is not reflecting , It is taking
only any where only default time out(i,e 5 seconds).
Could you please check and confirm , why it is not reflecting other than 5
seconds login time out.
I am using "derbyclient-10.13.1.1.jar" with client server mode communication
like,
ClientDataSource ds = new ClientDataSource();
ds.setLoginTimeout(15);
ds.setUser("TEST");
ds.setPassword("TEST123");
ds.setServerName("127.0.0.1");
ds.setDatabaseName("live");
ds.setPortNumber(1527);
Thanks,
Satyabrata Mohanty
> No support for setting connection timeout for a connection
> ----------------------------------------------------------
>
> Key: DERBY-6970
> URL: https://issues.apache.org/jira/browse/DERBY-6970
> Project: Derby
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 10.13.1.1
> Environment: Linux Operating system Resin App server
> Reporter: Satyabrata Mohanty
> Attachments: DERBY_6970.java
>
>
> https://stackoverflow.com/questions/44722659/providing-connection-time-out-in-derby-client-driver
> This is the link where i have put the details of my requirement. Basically my
> question is, how we can provide a timeout to connection, if connection object
> not established within that specific time it must get out from infinite
> waiting and resulting any exception or null, but seems to be there is no such
> functionality in derby till now. Request you to kindly look-into this and
> provide your inputs like if there is a way to achieve this then mention it
> with clear steps or else if its not implemented then when we can get this
> must have required feature in derby. Its really affecting our performance
> request you to kindly respond quickly.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
