[
http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12434718 ]
Knut Anders Hatlen commented on DERBY-1326:
-------------------------------------------
Bryan, I'm not sure I understand what impact this could have on
DERBY-51. DERBY-51 is about server shutdown, whereas this issue is
about a client opening a connection which has the side effect of
shutting down the engine.
> That is, it seems to me that a user might expect that if they shut
> down the Network Server, that when that call returned to them, their
> application could assume that the database was also shut down as of
> that point.
If the network server is started from command line and the user
invokes NetworkServerControl.shutdown() this is exactly what happens
in Derby 10.2. In 10.1, and in 10.2 when the server is not started
from command line, the server does not shut down the engine/databases
on shutdown. However, getConnection("...;shutdown=true") does not shut
down the server, only the engine.
I don't see that poisoning or not poisoning the threads should affect
that behaviour or "force our hands" in any way w.r.t. DERBY-51. When
the *server* at a later point is told to shut down, it is free to shut
down (or not to shut down) the *engine* regardless of threads with old
sessions hanging around. Also, threads with old sessions can be
present on the server for a long time after an engine shutdown even in
the current code (there is no call to Thread.interrupt() after the
engine has been shut down).
> Network server may abandon sessions when Derby system is shutdown and this
> causes intermittent hangs in the client
> ------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1326
> URL: http://issues.apache.org/jira/browse/DERBY-1326
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Reporter: Deepa Remesh
> Assigned To: Knut Anders Hatlen
> Attachments: derby-1326-cleanup_exceptions.diff, repro1326.java,
> resolve_DRDConnThread_conflict.diff, Restart.java, sessionMgmt1.diff,
> sessionMgmt1_and_nosessionsforclosedthreads.diff,
> unify_NSImpl_instances.diff, withNewThreadAndNoShutdownOfCurrentSession.diff
>
>
> This issue was found when working on DERBY-1219. More details can be found in
> the comments at http://issues.apache.org/jira/browse/DERBY-1219
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
