db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6815) Connection timeout
Date Sun, 07 Jun 2015 15:43:00 GMT

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

Rick Hillegas updated DERBY-6815:
---------------------------------
               Urgency: Normal  (was: Urgent)
    Bug behavior facts: Security

Thanks for raising this issue. I am not aware of a keep-alive timeout for network connections.
I am marking this as a Security issue because it could give rise to denial-of-service attacks.

I have also reduced the Urgency of this issue to Normal. That field causes a lot of confusion
to newcomers. The Urgency field is reserved for use by the release manager.

Thanks,
-Rick



> 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
>
> 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
(v6.3.4#6332)

Mime
View raw message