You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2018/03/01 03:05:00 UTC
[jira] [Commented] (DERBY-6985) Document how to configure the
keepAlive timeout on network sockets
[ https://issues.apache.org/jira/browse/DERBY-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381443#comment-16381443 ]
Rick Hillegas commented on DERBY-6985:
--------------------------------------
I have marked this issue as a documentation issue. The section in the Admin guide on derby.drda.keepAlive should note that the property determines whether the client Socket is marked setKeepAlive(true) or setKeepAlive(false). These are TCP/IP sockets and so it should be possible to configure their behavior via OS parameters. See, for instance, http://coryklein.com/tcp/2015/11/25/custom-configuration-of-tcp-socket-keep-alive-timeouts.html. In this case, the default value for tcp_keepalive_time appears to be 7200 seconds, that is, 2 hours.
> Document how to configure the keepAlive timeout on network sockets
> ------------------------------------------------------------------
>
> Key: DERBY-6985
> URL: https://issues.apache.org/jira/browse/DERBY-6985
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.14.1.0
> Reporter: Satyabrata Mohanty
> Priority: Major
> Attachments: Derby_Open_Connection.png
>
>
> Hi,
> Below is the complete description of the issue,
> * Running a java application which creates a good number of connections with derby on the machine X.
> * We are running the derby database server on the machine lets say Y.
> * We explicitly block the listening of 1527 port of system X traffics on system Y in the network until it thrown connection exception and then again established the network between the two systems.
> * After the java application has finished execution we found there are still some connections remained open in derby.
> * We can see open connections in derby although we have terminated the java application.
> * We have restarted derby to free up these connection.
> * Concern here is, how these connection are generated, is these connections are broken /stale connection made during the network reset, if YES then, how to these connection will be auto deleted or handled in derby ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)