[
https://issues.apache.org/jira/browse/DERBY-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16382836#comment-16382836
]
Rick Hillegas commented on DERBY-6985:
--------------------------------------
Can you include more of the stack trace produced when you exceed the maximum
number of open file descriptors? The limit on the number of file descriptors is
another operating system parameter which you can tweak.
Maybe it would be good to step back at this point and ask why your application
is leaking connections. Does your application fail to close connections when
they have finished their work? Is your application exiting abruptly without
gracefully shutting down the database?
> 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)
