Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <6812328.1150465771282.JavaMail.jira@brutus>
Date: Fri, 16 Jun 2006 13:49:31 +0000 (GMT+00:00)
From: "John H. Embretsen (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1326) Network server may abandon sessions
 when Derby system is shutdown and this causes intermittent hangs in the
 client
In-Reply-To: <9452366.1147714146274.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1326?page=comments#action_12416494 ] 

John H. Embretsen commented on DERBY-1326:
------------------------------------------

> Deepa Remesh commented:
> -----------------------

[snip]

> From  current behaviour, we do not shutdown network server when we shutdown Derby. Does anyone know if there is any plan to do as indicated by the comment: "Want to use Monitor.startModule, so it can all get shutdown when cloudscape shuts down, but can't get it working right now." ? 


Speaking of current behaviour, here are some observations I have made recently:

a) In the "embedded server using properties" scenario, the Network Server starts when the embedded driver is loaded and stops when it is "unloaded", i.e. when the Derby system is shut down: DriverManager.getConnection("jdbc:derby:;shutdown=true");

b) In the "embedded server using NetworkServerControl API" scenario, the Network server of course starts when NetworkServerControl.start() is called, and stops when shutdown() is called. However, if the Derby system is shut down (by loading the embedded driver and doing as shown above), clients can no longer connect (getting "No suitable driver". Why?). The Network Server port seems to be listening on the same port still, though, according to netstat. Then, if I try to restart the server using the API (without calling shutdown() first), I get the message "Could not listen on port 1527 on host 0.0.0.0.". This makes sense, since the port is already in use. However, after start() is called the second time, clients _are_ in fact able to connect. There seems to be something happening when start() is called, even if the port is busy, that is needed to make the server able to accept connections again.

I have not done any code inspection in these cases, so I don't know if this is very helpful with regards to this Jira issue. I just reacted when I saw the above comment.


> 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
>         Type: Bug

>   Components: Network Server
>     Reporter: Deepa Remesh
>     Assignee: Bryan Pendleton
>  Attachments: repro1326.java, resolve_DRDConnThread_conflict.diff, 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