[jira] [Updated] (DERBY-5271) Client may hang if the server crashes due to a java.lang.Error

["Kristian Waagan (JIRA)" <ji...@apache.org>]

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

Kristian Waagan updated DERBY-5271:
-----------------------------------

    Attachment: derby-5271-1a-inital_fix_proposal.diff

Attaching an initial fix proposal with patch 1a to get the discussion started.
It addresses the problem I encountered, where the client hung due to an OOME on the server (same machine/JVM). This was part of a test run, and I had to manually kill the JVM to get the test script to continue (I think the first time this happened the process was left untouched for more than 12 hours).

> 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
>            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