db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5271) Client may hang if the server crashes due to a java.lang.Error
Date Sun, 12 Jun 2011 04:29:51 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048225#comment-13048225

Dag H. Wanvik commented on DERBY-5271:

Agreed. Just wondering, I haven't studied the code: if there a chance that trying to close
the session might make the *server* hang (and not get to throw Error)? 

> 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:
>            Reporter: Kristian Waagan
>            Priority: Minor
>         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


View raw message