[
https://issues.apache.org/jira/browse/DERBY-6815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569189#comment-16569189
]
Rick Hillegas commented on DERBY-6815:
--------------------------------------
Linking to DERBY-6985, which gives some tips on how to adjust the operating
system's TCP keepAlive settings. Hope this helps.
> Connection timeout
> ------------------
>
> Key: DERBY-6815
> URL: https://issues.apache.org/jira/browse/DERBY-6815
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.11.1.1
> Reporter: sagar
> Priority: Major
>
> Is there a timeout property for derby connections on the server side?
> That is if a client does not close a connection, derby server should close it
> automatically after a particular timeout.
> Because number of unclosed connections will increase the number of threads
> and memory usage.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
