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 2004/10/27 18:49:32 UTC
[jira] Created: (DERBY-51) Need NetworkServerControl shutdown API method that does not shutdown cloudscape
Need NetworkServerControl shutdown API method that does not shutdown cloudscape
-------------------------------------------------------------------------------
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
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 derby. if false do not shutdown derby
* @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
-
If you want more information on JIRA, or have a bug to report 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 "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
[jira] Commented: (DERBY-51) Need NetworkServerControl shutdown API
method that does not shutdown derby embedded
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-51?page=comments#action_12365150 ]
Kathey Marsden commented on DERBY-51:
-------------------------------------
Well I guess I didn't notice David's comment on this issue when he made it (in May).
David said
>code that shuts down embedded seems to be commented out -- see the commented out code at the end of >NetworkServerControlImpl.blockingStart(), starting with "// Shutdown Cloudscape".
I am a little surprised and wonder.
Has it always been this way since 10.0?
Are we shutting down cleanly when we start from the command line?
>Is it that we need an API that makes this an optional behavior? Or are things OK as they stand?
I tend to think we need an api to shutdown embedded with network server. Othewise it seems likely that folks will assume it gets shutdown.
> 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
[jira] Commented: (DERBY-51) Need NetworkServerControl shutdown API
method that does not shutdown derby embedded
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ 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 Kathey Marsden <km...@sbcglobal.net>.
Bryan Pendleton wrote:
>
> 1) There are two basic configurations of interest here:
> a) In the simple Network Server case, the Network Server process
> is providing access to the database(s) over DRDA
> b) In the dual-access configuration, an application which has
> established embedded access to the database(s) is also
> providing networked access to those same database(s) by
> creating a Network Server object in the same application.
>
I thought it worth mentioning that there are two ways of achieving
configuration b which will need to be considered.
1) Server is started with the API.
2) Server is started with derby.drda.startNetworkServer=true
It is not clear then if it should shut down when derby is
shutdown. It creates a sort of chicken and egg question.
I think your summary is good and agree that if we can figure out how to
do the right thing based on the configuration that is best.
Re: [jira] Commented: (DERBY-51) Need NetworkServerControl shutdown
API method that does not shutdown derby embedded
Posted by Stanley Bradbury <St...@gmail.com>.
Oystein Grovlen - Sun Norway wrote:
> Bryan Pendleton wrote:
>
>> 1) There are two basic configurations of interest here:
>> a) In the simple Network Server case, the Network Server process
>> is providing access to the database(s) over DRDA
>> b) In the dual-access configuration, an application which has
>> established embedded access to the database(s) is also
>> providing networked access to those same database(s) by
>> creating a Network Server object in the same application.
>>
>> 2) Currently, when the Network Server is shut down, it does NOT
>> shut down the database(s) that it has been providing access to.
>> This is important for users of the dual-access configuration,
>> because they may well be continuing to access the database(s)
>> through the embedded connection.
>
>
> It is a bit unfortunate that the same term (shutdown) is used in both
> cases. It would have better if one used start/stop for the network
> server and reserved shutdown for the database. I guess it is too late
> to do anything with that.
>
>> 3) Unfortunately, in the simple Network Server case, this behavior
>> is very non-intuitive, as most users would expect that when
>> they shut down the Network Server in a clean fashion, that this
>> would also shut down the database(s) in a clean fashion.
>>
>> 4) Unconditionally changing behavior (2) is worrisome, because it
>> could affect existing applications (of either configuration).
>> We should not take such a step lightly.
>>
>> I hope that there is general agreement about the above, so please
>> indicate if I've got it wrong.
>>
>> In terms of what changes to make to the behavior of the Network Server,
>> it seems that there are two basic proposals:
>> - Don't add any new flags or arguments or commands; just make the
>> Network Server shutdown do the right thing. Of course, this depends
>> on whether we can agree on what the right thing is in all cases,
>> and on whether the code has enough information to be able to do it.
>> - Allow the end user to choose the shutdown behavior, by indicating
>> whether they just want to shut down the Network Server, or whether
>> they also want to shut down the database(s).
>>
>> My preference would be the former, because I think it would be less
>> complex, easier to use, and simpler to document. I think that when
>> the simple Network Server shuts down, it should shut down the databases
>> it was providing access to, but when the Network Server has been started
>> in a dual-access configuration in which there is also embedded access to
>> the database(s) within the same application, the Network Server should
>> *not* shut down the databases when it is shutting down.
>
>
> What if the existing method is changed to shut down the database if
> there is no other open connections to it? We would then probably have
> to add an option to force a shutdown even when there is open
> connections. So maybe this is just a variant of the second
> alternative above.
>
At a minimum I think we should implement two shutdown modes (by adding
one new NetworkServerControl flag). The current command does clean up
including shutdown of all the databases (just like the parameter
implies: ..NetworkServerControl -shutdown) the new mode just ends the
Server (like is done now: ..NetworkServerControl -killServer ?). Using
a term like 'kill' for the mode that does *NOT* shutdown down databases
will indicate that is is an more abrupt ending.
Issuing a warning and allowing an abort of the shutdown/kill when there
are existing connections is a nicety but I think less important than
having a clean (from a database standpoint) shutdown. I would argue
that people that knowingly implement an embedded server architecture
(i.e. dual-access configuration in which there is also embedded access
to the database(s) within the same application) are savvy enough to
understand the implications of dual-access and mange it in an
appropriate manner.
Re: [jira] Commented: (DERBY-51) Need NetworkServerControl shutdown
API method that does not shutdown derby embedded
Posted by Oystein Grovlen - Sun Norway <Oy...@Sun.COM>.
Bryan Pendleton wrote:
> 1) There are two basic configurations of interest here:
> a) In the simple Network Server case, the Network Server process
> is providing access to the database(s) over DRDA
> b) In the dual-access configuration, an application which has
> established embedded access to the database(s) is also
> providing networked access to those same database(s) by
> creating a Network Server object in the same application.
>
> 2) Currently, when the Network Server is shut down, it does NOT
> shut down the database(s) that it has been providing access to.
> This is important for users of the dual-access configuration,
> because they may well be continuing to access the database(s)
> through the embedded connection.
It is a bit unfortunate that the same term (shutdown) is used in both
cases. It would have better if one used start/stop for the network
server and reserved shutdown for the database. I guess it is too late to
do anything with that.
> 3) Unfortunately, in the simple Network Server case, this behavior
> is very non-intuitive, as most users would expect that when
> they shut down the Network Server in a clean fashion, that this
> would also shut down the database(s) in a clean fashion.
>
> 4) Unconditionally changing behavior (2) is worrisome, because it
> could affect existing applications (of either configuration).
> We should not take such a step lightly.
>
> I hope that there is general agreement about the above, so please
> indicate if I've got it wrong.
>
> In terms of what changes to make to the behavior of the Network Server,
> it seems that there are two basic proposals:
> - Don't add any new flags or arguments or commands; just make the
> Network Server shutdown do the right thing. Of course, this depends
> on whether we can agree on what the right thing is in all cases,
> and on whether the code has enough information to be able to do it.
> - Allow the end user to choose the shutdown behavior, by indicating
> whether they just want to shut down the Network Server, or whether
> they also want to shut down the database(s).
>
> My preference would be the former, because I think it would be less
> complex, easier to use, and simpler to document. I think that when
> the simple Network Server shuts down, it should shut down the databases
> it was providing access to, but when the Network Server has been started
> in a dual-access configuration in which there is also embedded access to
> the database(s) within the same application, the Network Server should
> *not* shut down the databases when it is shutting down.
What if the existing method is changed to shut down the database if
there is no other open connections to it? We would then probably have
to add an option to force a shutdown even when there is open
connections. So maybe this is just a variant of the second alternative
above.
--
Øystein
Re: [jira] Commented: (DERBY-51) Need NetworkServerControl shutdown
API method that does not shutdown derby embedded
Posted by Bryan Pendleton <bp...@amberpoint.com>.
>> I am less convinced that it can't be changed. The alternate approach to
>> the one I proposed would be:
I feel like there is general consensus about this topic, although that
might be surprising because several opinions and proposals have been
stated so far. Let me state what I think the general consensus is, so
that we can see how best to move forward.
1) There are two basic configurations of interest here:
a) In the simple Network Server case, the Network Server process
is providing access to the database(s) over DRDA
b) In the dual-access configuration, an application which has
established embedded access to the database(s) is also
providing networked access to those same database(s) by
creating a Network Server object in the same application.
2) Currently, when the Network Server is shut down, it does NOT
shut down the database(s) that it has been providing access to.
This is important for users of the dual-access configuration,
because they may well be continuing to access the database(s)
through the embedded connection.
3) Unfortunately, in the simple Network Server case, this behavior
is very non-intuitive, as most users would expect that when
they shut down the Network Server in a clean fashion, that this
would also shut down the database(s) in a clean fashion.
4) Unconditionally changing behavior (2) is worrisome, because it
could affect existing applications (of either configuration).
We should not take such a step lightly.
I hope that there is general agreement about the above, so please
indicate if I've got it wrong.
In terms of what changes to make to the behavior of the Network Server,
it seems that there are two basic proposals:
- Don't add any new flags or arguments or commands; just make the
Network Server shutdown do the right thing. Of course, this depends
on whether we can agree on what the right thing is in all cases,
and on whether the code has enough information to be able to do it.
- Allow the end user to choose the shutdown behavior, by indicating
whether they just want to shut down the Network Server, or whether
they also want to shut down the database(s).
My preference would be the former, because I think it would be less
complex, easier to use, and simpler to document. I think that when
the simple Network Server shuts down, it should shut down the databases
it was providing access to, but when the Network Server has been started
in a dual-access configuration in which there is also embedded access to
the database(s) within the same application, the Network Server should
*not* shut down the databases when it is shutting down.
This does change the behavior in the simple Network Server case, but I
think it changes it to the behavior that is what most users expect.
An interesting question is whether shutting down the database(s) could
fail, and, if so, what the Network Server shutdown code should do if it
encounters such a failure: does it shutdown anyway? Does it abort the
shutdown and stay up and try to tell the user about the problem?
I'd like to stop here, to see whether people feel I've captured the
discussion correctly up to this point.
thanks,
bryan
Re: [jira] Commented: (DERBY-51) Need NetworkServerControl shutdown
API method that does not shutdown derby embedded
Posted by John Embretsen <Jo...@Sun.COM>.
Kathey Marsden wrote:
> John H. Embretsen (JIRA) wrote:
>
>> Kathey Marsden commented:
>>> I don't think the default behaviour for the API shutdown can be changed at this point.
>>>
>>>
>> Why is that?
>>
>>
>>
> My thinking was that users may be dependent on the existing behavour,
> but if it is documented that way ...
>
>> Specifically, I found the following statement in the admin guide, http://db.apache.org/derby/docs/dev/adminguide/tadminconfigshuttingdownthenetworkserver.html, for trunk:
>>
>>
>>
> I am less convinced that it can't be changed. The alternate approach to
> the one I proposed would be:
>
> 1) Leave DERBY-51 open as is.
> 2) Log a bug that network server does not shutdown databases properly
> when network server is shutdown.
> 3) Determine what the behaviour is/should be when embedded is shutdown
> or network server is shutdown if Network Server was started with the
> derby.drda.startNetworkServer property.
>
> This approach poses some risk to applications that might have been
> relying on the bug (2) but it could be mitigated since we document it
> this way and doing this way makes sense. Proper notification in the
> Release Notes would be required and we probably should give early
> notification to the user base.
>
> How should we proceed?
Well, I think your alternate approach makes more sense, but I don't have very
strong feelings about it.
Either way, I believe having the same default behavior for the CLI (command
line interface) and the API is a positive thing. Not having the CLI shut down
Derby when the network server is shut down (via the CLI) does not make much
sense to me...
However, other people on the list seem to like your first suggestion, so I
understand if that is what we end up with.
--
John
Re: [jira] Commented: (DERBY-51) Need NetworkServerControl shutdown
API method that does not shutdown derby embedded
Posted by Kathey Marsden <km...@sbcglobal.net>.
John H. Embretsen (JIRA) wrote:
>Kathey Marsden commented:
>
>
>
>>I don't think the default behaviour for the API shutdown can be changed at this point.
>>
>>
>
>Why is that?
>
>
>
My thinking was that users may be dependent on the existing behavour,
but if it is documented that way ...
>Specifically, I found the following statement in the admin guide, http://db.apache.org/derby/docs/dev/adminguide/tadminconfigshuttingdownthenetworkserver.html, for trunk:
>
>
>
I am less convinced that it can't be changed. The alternate approach to
the one I proposed would be:
1) Leave DERBY-51 open as is.
2) Log a bug that network server does not shutdown databases properly
when network server is shutdown.
3) Determine what the behaviour is/should be when embedded is shutdown
or network server is shutdown if Network Server was started with the
derby.drda.startNetworkServer property.
This approach poses some risk to applications that might have been
relying on the bug (2) but it could be mitigated since we document it
this way and doing this way makes sense. Proper notification in the
Release Notes would be required and we probably should give early
notification to the user base.
How should we proceed?
[jira] Commented: (DERBY-51) Need NetworkServerControl shutdown API
method that does not shutdown derby embedded
Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-51?page=comments#action_12375072 ]
John H. Embretsen commented on DERBY-51:
----------------------------------------
Kathey Marsden commented:
> I don't think the default behaviour for the API shutdown can be changed at this point.
Why is that?
> 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))
If we don't change the default API behavior then we also need to do
4) Correct the manuals.
Specifically, I found the following statement in the admin guide, http://db.apache.org/derby/docs/dev/adminguide/tadminconfigshuttingdownthenetworkserver.html, for trunk:
<quote>
If user authentication is disabled, a Derby database will shut down normally when the Network Server is shut down. If user authentication is enabled, you must explicitly shut down the database before shutting down the Network Server by specifying a valid Derby user name and password.
</quote>
> 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
[jira] Commented: (DERBY-51) Need NetworkServerControl shutdown API method that does not shutdown derby embedded
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-51?page=comments#action_65710 ]
David Van Couvering commented on DERBY-51:
------------------------------------------
I can't seem to reproduce this behavior (see attached modification to the test derbynet/NSInSameJVM.java). I also looked in the code for NetworkServerControlImpl, and the code that shuts down embedded seems to be commented out -- see the commented out code at the end of NetworkServerControlImpl.blockingStart(), starting with "// Shutdown Cloudscape".
So, unless I missed something, it appears that right now the Derby system does *not* get shut down when the Network Server is stopped.
Is it that we need an API that makes this an optional behavior? Or are things OK as they stand?
> 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
[jira] Updated: (DERBY-51) Need NetworkServerControl shutdown API method that does not shutdown derby embedded
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-51?page=history ]
Kathey Marsden updated DERBY-51:
--------------------------------
Summary: Need NetworkServerControl shutdown API method that does not shutdown derby embedded (was: Need NetworkServerControl shutdown API method that does not shutdown cloudscape)
Description:
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
was:
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 derby. if false do not shutdown derby
* @exception Exception throws an exception if an error occurs
*/
public void shutdown(boolean derbyShutdown) throws Exception
> 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
>
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-51) Need NetworkServerControl shutdown API method that does not shutdown derby embedded
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-51?page=all ]
David Van Couvering updated DERBY-51:
-------------------------------------
Attachment: NSinSameJVM.java
This modification to NSinSameJVM.java ensures that an embedded connection is usable after
shutdown of the Network Server. Running the test produced no failures...
> 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