[
https://issues.apache.org/jira/browse/DERBY-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16380361#comment-16380361
]
Satyabrata Mohanty commented on DERBY-6985:
-------------------------------------------
Hi,
By doing some more searching on this, we found one property
derby.drda.keepAlive
This property is by default true.
"It Indicates whether SO_KEEPALIVE is enabled on sockets. The keepAlive
mechanism is used to detect when clients disconnect unexpectedly. A _keepalive
probe_ is sent to the client if a long time *(by default, more than two hours)*
passes with no other data being sent or received. The derby.drda.keepAlive
property is used to detect and clean up connections for clients on powered-off
machines or clients that have disconnected unexpectedly"
Does the default time (more than two hours ) mentioned is configurable, is
there any property or any process available in derby to reduce this value ? If
not then how this default values are considered, does it depends upon the OS?
This issue may be related to this issue
https://issues.apache.org/jira/browse/DERBY-6815.
Requesting you to please look-into this and also let us know for any
information you need from our side.
Thanks,
Satyabrata
> Connection never released from Derby
> ------------------------------------
>
> Key: DERBY-6985
> URL: https://issues.apache.org/jira/browse/DERBY-6985
> Project: Derby
> Issue Type: Bug
> 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)
