[
https://issues.apache.org/jira/browse/DERBY-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-5271:
-----------------------------------
Fix Version/s: 10.9.0.0
Committed patch 1a to trunk with revision 1158108.
I plan to backport this fix.
Regarding making the server hang, I can't guarantee that it won't happen. If it
happens it would hopefully affect only the worker thread that crashed. Most of
the Error subclasses are pretty serious and the JVM will come down in many
cases. OOME isn't necessarily one of these - what happens depends on the nature
of the shortage and in which threads an OOME is raised. Further, a single hung
ClientThread may not be a problem, assuming that database resources (like
locks) have been released.
> 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.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
