db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6970) No support for setting connection timeout for a connection
Date Sun, 22 Oct 2017 16:25:00 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214373#comment-16214373

Bryan Pendleton commented on DERBY-6970:

What is the exact exception that you get when you receive the 5 second timeout? Use the coding
technique described here to ensure that you are capturing all the details, and attach the
results to the issue: https://wiki.apache.org/db-derby/UnwindExceptionChain

Also, download the Derby "debug" jars so that you can run your program under a Java debugger
(or download and build the Derby source code from Subversion). Then you can set a breakpoint
in your client program at the moment that you issue the connection request, and also at the
moment, 5 seconds later, that you receive the login timeout, and you can examine the Derby
data structures to see what values are present in those data structures for the login timeout

> 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:
>         Environment: Linux Operating system Resin App server
>            Reporter: Satyabrata Mohanty
>         Attachments: DERBY_6970.java, 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

View raw message