db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satyabrata Mohanty (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6985) Connection never released from Derby
Date Wed, 28 Feb 2018 07:18:00 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Satyabrata Mohanty updated DERBY-6985:
    Affects Version/s:

> Connection never released from Derby
> ------------------------------------
>                 Key: DERBY-6985
>                 URL: https://issues.apache.org/jira/browse/DERBY-6985
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions:
>            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 ?
>  * Derby version used

This message was sent by Atlassian JIRA

View raw message