db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francois Orsini <francois.ors...@gmail.com>
Subject Re: [jira] Commented: (DERBY-4377) Developer's Guide statement on shutting down Derby needs qualification
Date Tue, 29 Sep 2009 22:46:08 GMT
On Tue, Sep 29, 2009 at 11:17 AM, Dag H. Wanvik <Dag.Wanvik@sun.com> wrote:

> "Francois Orsini (JIRA)" <jira@apache.org> writes:
> > If you have enabled Derby's BUILTIN user authentication and created
> > some user at the system level (for example, by setting some username
> > and password in the derby.properties file), you will need to specify
> > credentials (e.g. username and password) in order to shut down a
> > Derby system.
> So if I understand this correctly; if users are defined only on the
> database level (but BUILTIN user authentication is defined at the
> system level), it will still be possible to shut down a Derby system
> *without* supplying credentials?

Nope - that is not what was meant.

On the contrary, if you enable authentication at the system level and don't
have any users created in derby.properties, you won't be able to shutdown a
Derby instance at all via 'jdbc:derby:;shutdown=true' (besides exiting
or/and killing the VM process). Users' credentials defined as part of a
database are not involved when shutting down a Derby instance (not a

View raw message