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?
