[
https://issues.apache.org/jira/browse/DERBY-6094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595535#comment-13595535
]
Dag H. Wanvik edited comment on DERBY-6094 at 3/7/13 4:27 AM:
--------------------------------------------------------------
Good tests. Minor: comment say 5 seconds sleep, code says 2.
I don't quite understand this result:
Stopping server...
Starting server with timeout 10
:
Setting timeout 10 on local connector
Testing derby6094.Derby6094$DriverManagerConnector(
jdbc:derby://localhost:8246/memory:db1 )
java.sql.SQLNonTransientConnectionException: SQLState = 08001. Message
= java.net.ConnectException : \
Error connecting to server localhost on port 8246 with message
Connection refused: connect.
Experiment took 1030 milliseconds.
If both the client and the server side timeout is 10 seconds (I presume only
the client side one sets any actual timeout: on the socket) and the
authenticator sleeps only 2 (or 5) seconds, why the failure?
Another question: You fork a server, but the test has unused code for starting
the server via the API in the same VM. Have you seen a difference in behavior
there?
was (Author: dagw):
Good tests. Minor: comment say 5 seconds sleep, code says 2.
I don't quite understand this result:
Stopping server...
Starting server with timeout 10
:
Setting timeout 10 on local connector
Testing derby6094.Derby6094$DriverManagerConnector(
jdbc:derby://localhost:8246/memory:db1 )
java.sql.SQLNonTransientConnectionException: SQLState = 08001. Message
= java.net.ConnectException : \
Error connecting to server localhost on port 8246 with message
Connection refused: connect.
Experiment took 1030 milliseconds.
If both the client and the server side timeout is 10 seconds and the
authenticator sleeps only 2 (or 5) seconds, why the failure?
Another question: You fork a server, but the test has unused code for starting
the server via the API in the same VM. Have you seen a difference in behavior
there?
> Derby ignores DriverManager.setLoginTimeout()
> ---------------------------------------------
>
> Key: DERBY-6094
> URL: https://issues.apache.org/jira/browse/DERBY-6094
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Attachments: LoginTimeoutTest.java, LoginTimeoutTest.java,
> LoginTimeoutTest.java, LoginTimeoutTest.java
>
>
> If you set a login timeout using the DriverManager, Derby ignores the
> setting. I will attach a test case which shows this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
