db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DERBY-5271) Client may hang if the server crashes due to a java.lang.Error
Date Tue, 23 Aug 2011 09:10:29 GMT

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

Kristian Waagan resolved DERBY-5271.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.8.1.6

Backported to 10.8 with revision 1160590.
Resolving issue.

> Client may hang if the server crashes due to a java.lang.Error
> --------------------------------------------------------------
>
>                 Key: DERBY-5271
>                 URL: https://issues.apache.org/jira/browse/DERBY-5271
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions: 10.9.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.8.1.6, 10.9.0.0
>
>         Attachments: derby-5271-1a-inital_fix_proposal.diff
>
>
> When certain types of errors are raised while the network server is processing a client
request, the server is left in a semi-degraded state. The problem this issue is concerned
with, is that the client socket is kept open even though the server in a kind of degraded
state (server JVM still alive). This causes the client to hang, until the server JVM is killed,
in a read-call on the socket.
> I'm able to reproduce this with an OOME being raised on the server.
> In my opinion, hanging when there is no chance of progression is bad behavior. Furthermore,
it causes trouble for automated testing.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message