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 "Mike Matrigali (Updated) (JIRA)" <ji...@apache.org> on 2012/02/16 21:24:59 UTC
[jira] [Updated] (DERBY-5330) derby.log created with shutdown
message only, possibly overwriting existing file
[ https://issues.apache.org/jira/browse/DERBY-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-5330:
----------------------------------
Component/s: Tools
first check if this is an ij specific problem, thus made tools component.
> derby.log created with shutdown message only, possibly overwriting existing file
> --------------------------------------------------------------------------------
>
> Key: DERBY-5330
> URL: https://issues.apache.org/jira/browse/DERBY-5330
> Project: Derby
> Issue Type: Improvement
> Components: Tools
> Affects Versions: 10.9.0.0
> Reporter: Kristian Waagan
> Priority: Minor
>
> Recently I have noticed that when I use ij to perform some administrative tasks on a network server, I end up with a derby.log file in my current directory. It has only one message:
> $ cat derby.log
> ----------------------------------------------------------------
> Thu Jul 14 10:41:55 CEST 2011: Shutting down Derby engine
> ----------------------------------------------------------------
> $
> I never used the embedded driver in the ij session, but derby.jar is available on the classpath.
> Now, that's junk lying around and isn't such a big deal (although annoying). However, I have also gotten derby.log from the network server overwritten by this - and that's worse.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira