You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <de...@db.apache.org> on 2006/04/19 01:55:23 UTC

[jira] Commented: (DERBY-51) Need NetworkServerControl shutdown API method that does not shutdown derby embedded

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

Kathey Marsden commented on DERBY-51:
-------------------------------------

After some discussion on this issue and a bit of minimal testing I think that the following situation exists. The default shutdown API  and command line shutdown is not shutting down the embedded database and so this particular issue  which prompted this request  does not exist.   I don't think the default behaviour for the API shutdown can be changed at this point.

 So I suggest we do the following:

1) Close this issue as invalid
2) Open a new issue to add an API  public void shutdown(boolean derbyShutdown) 
3) Make it clear in the javadoc that  public void shutdown()  does not shutdown Derby (calls shutdown(false)) 


Also we can file a bug that  the NetworkServerControl command line shutdown should shutdown embedded if the server was started from the command line. I think it is safe to shutdown in this case and maybe for any command line shutdown.

Does this should reasonable?





> Need NetworkServerControl shutdown API method that does not shutdown derby embedded
> -----------------------------------------------------------------------------------
>
>          Key: DERBY-51
>          URL: http://issues.apache.org/jira/browse/DERBY-51
>      Project: Derby
>         Type: Improvement

>   Components: Network Server
>     Versions: 10.0.2.0
>     Reporter: Kathey Marsden
>  Attachments: NSinSameJVM.java
>
> In an applcation server environment where both Network Server 
> and Embedded connections are being used it is a problem when 
> Network server is shutdown and deregisters the embedded driver 
> and shutsdown the databases.
> this would be the signature
> /**
> * Shutdown a Network Server.
> * Shuts down the Network Server listening on the port and InetAddress
> * specified in the constructor for this NetworkServerControl object.
> *
> * @param derbyShutdown if true, shutsdown the derby embedded system . if false do not shutdown derby embeddded system
> * @exception Exception	throws an exception if an error occurs
> */
> public void shutdown(boolean derbyShutdown) throws Exception

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


Re: [jira] Commented: (DERBY-51) Need NetworkServerControl shutdown API method that does not shutdown derby embedded

Posted by Bryan Pendleton <bp...@amberpoint.com>.
Kathey Marsden (JIRA) wrote:
> Does this should reasonable?

Yes, I think this is a good plan.

bryan




Re: [jira] Commented: (DERBY-51) Need NetworkServerControl shutdown API method that does not shutdown derby embedded

Posted by "Bernt M. Johnsen" <Be...@Sun.COM>.
>>>>>>>>>>>> Kathey Marsden (JIRA) wrote (2006-04-18 23:55:23):
>  So I suggest we do the following:
> 
> 1) Close this issue as invalid
> 2) Open a new issue to add an API  public void shutdown(boolean derbyShutdown) 
> 3) Make it clear in the javadoc that  public void shutdown()  does not shutdown Derby (calls shutdown(false)) 
> 
> 
> Also we can file a bug that the NetworkServerControl command line
> shutdown should shutdown embedded if the server was started from the
> command line. I think it is safe to shutdown in this case and maybe
> for any command line shutdown.
> 
> Does this should reasonable?

+1

-- 
Bernt Marius Johnsen, Database Technology Group, 
Staff Engineer, Technical Lead Derby/Java DB
Sun Microsystems, Trondheim, Norway