Derby
  1. Derby
  2. DERBY-4755

DERBY-4601 added a new message to derby.log during engine shutdown and it changed the database shutdown message. Need to update docs with that information

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.7.1.1
    • Fix Version/s: 10.7.1.1
    • Component/s: Documentation
    • Labels:
      None

      Description

      DERBY-4601 added a new message to derby.log during engine shutdown and it changed the database shutdown message. Need to update docs with that information. I have found 2 places in our docs where we show examples of shutdown messages
      1)In Getting started Guide, under Creating a Derby database and running SQL statements section, we show a typical startup and shutdown message. That section will need to change
      2)In Derby Developer's Guide, under section Derby System -> Shutting down the system

      An eg of engine shutdown message in derby.log is
      2010-07-23 18:59:24.078 GMT Thread[main,5,main] :Shutting down Derby Engine

      An eg of database shutdown message is as follows
      2010-07-20 17:23:55.171 GMT:
      Shutting down instance 80220011-0129-f0e1-f479-0000000c5ef0 on database directory C:\p4clients\svnmain\client2\trunk\systest\out142\dbs\tours3 with class loader sun.misc.Launcher$AppClassLoader@3f6e3f6e
      (Notice that this message includes the name of the db getting shutdown. Before the changes for DERBY-4601 went in, we didn't include the name of the database)

      1. derby.log
        4 kB
        Mamta A. Satoor
      2. space.diff
        2 kB
        Knut Anders Hatlen

        Issue Links

          Activity

          Hide
          Knut Anders Hatlen added a comment -

          [bulk update] Close all resolved issues that haven't been updated for more than one year.

          Show
          Knut Anders Hatlen added a comment - [bulk update] Close all resolved issues that haven't been updated for more than one year.
          Hide
          Kim Haase added a comment -

          This work was completed as part of DERBY-4826.

          Show
          Kim Haase added a comment - This work was completed as part of DERBY-4826 .
          Hide
          Knut Anders Hatlen added a comment -

          Yes, I saw them in that order, but note that I did an explicit shutdown of the database before the system shutdown. If I do a system shutdown while the database is still booted, I see the messages in the same order as you did.

          Show
          Knut Anders Hatlen added a comment - Yes, I saw them in that order, but note that I did an explicit shutdown of the database before the system shutdown. If I do a system shutdown while the database is still booted, I see the messages in the same order as you did.
          Hide
          Kim Haase added a comment -

          You're quite right, Knut, that the messages look untidy. They've been that way forever, but it would be good if that output could be changed.

          The order of the shutdown messages puzzles me, though. Do you really see the instance shutdown message before the engine shutdown message? I always see this order:

          ----------------------------------------------------------------
          Mon Nov 01 09:35:16 EDT 2010: Shutting down Derby engine
          ----------------------------------------------------------------
          Mon Nov 01 09:35:16 EDT 2010:
          Shutting down instance a816c00e-012c-07a5-449c-000000baf358 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e
          ----------------------------------------------------------------

          Show
          Kim Haase added a comment - You're quite right, Knut, that the messages look untidy. They've been that way forever, but it would be good if that output could be changed. The order of the shutdown messages puzzles me, though. Do you really see the instance shutdown message before the engine shutdown message? I always see this order: ---------------------------------------------------------------- Mon Nov 01 09:35:16 EDT 2010: Shutting down Derby engine ---------------------------------------------------------------- Mon Nov 01 09:35:16 EDT 2010: Shutting down instance a816c00e-012c-07a5-449c-000000baf358 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e ----------------------------------------------------------------
          Hide
          Knut Anders Hatlen added a comment -

          I went ahead and removed the blank line. Committed revision 1029579.

          Now I see this in derby.log after a sequence of booting a database, shutting it down, and finally shutting the engine down:

          ----------------------------------------------------------------
          Mon Nov 01 10:00:17 CET 2010:
          Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alpha - (1): instance a816c00e-012c-06aa-5f68-00000369adb8
          on database directory /tmp/db with class loader sun.misc.Launcher$AppClassLoader@17182c1
          Loaded from file:/code/derby/trunk0/classes/
          java.vendor=Sun Microsystems Inc.
          java.runtime.version=1.6.0_21-b06
          Database Class Loader started - derby.database.classpath=''
          ----------------------------------------------------------------
          Mon Nov 01 10:00:33 CET 2010:
          Shutting down instance a816c00e-012c-06aa-5f68-00000369adb8 on database directory /tmp/db with class loader sun.misc.Launcher$AppClassLoader@17182c1
          ----------------------------------------------------------------
          Mon Nov 01 10:00:44 CET 2010: Shutting down Derby engine
          ----------------------------------------------------------------

          I still feel the messages look a bit untidy. Especially the boot message. For example, the line that specifies the version, there's not much point in mentioning both Apache and Derby twice, so perhaps we could simplify it to something like this:

          Booting Apache Derby 10.7.0.0 alpha - (1): instance a816c00e-012c-06aa-5f68-00000369adb8

          Show
          Knut Anders Hatlen added a comment - I went ahead and removed the blank line. Committed revision 1029579. Now I see this in derby.log after a sequence of booting a database, shutting it down, and finally shutting the engine down: ---------------------------------------------------------------- Mon Nov 01 10:00:17 CET 2010: Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alpha - (1): instance a816c00e-012c-06aa-5f68-00000369adb8 on database directory /tmp/db with class loader sun.misc.Launcher$AppClassLoader@17182c1 Loaded from file:/code/derby/trunk0/classes/ java.vendor=Sun Microsystems Inc. java.runtime.version=1.6.0_21-b06 Database Class Loader started - derby.database.classpath='' ---------------------------------------------------------------- Mon Nov 01 10:00:33 CET 2010: Shutting down instance a816c00e-012c-06aa-5f68-00000369adb8 on database directory /tmp/db with class loader sun.misc.Launcher$AppClassLoader@17182c1 ---------------------------------------------------------------- Mon Nov 01 10:00:44 CET 2010: Shutting down Derby engine ---------------------------------------------------------------- I still feel the messages look a bit untidy. Especially the boot message. For example, the line that specifies the version, there's not much point in mentioning both Apache and Derby twice, so perhaps we could simplify it to something like this: Booting Apache Derby 10.7.0.0 alpha - (1): instance a816c00e-012c-06aa-5f68-00000369adb8
          Hide
          Kim Haase added a comment -

          Yes, I think you're right about that, Knut. We can do without the blank line if the horizontal line is there.

          I also notice that the line about the thread that was in the original message seems to have gone away –

          Thu Sep 30 17:03:21 EDT 2010 Thread[main,5,main]

          This is probably a good thing, since its meaning was not clear.

          Show
          Kim Haase added a comment - Yes, I think you're right about that, Knut. We can do without the blank line if the horizontal line is there. I also notice that the line about the thread that was in the original message seems to have gone away – Thu Sep 30 17:03:21 EDT 2010 Thread [main,5,main] This is probably a good thing, since its meaning was not clear.
          Hide
          Knut Anders Hatlen added a comment -

          The horizontal line (-----) after the startup message is part of the shutdown message. Is the blank line needed at all? I'd assume the horizontal line would be a good enough visual separator.

          Show
          Knut Anders Hatlen added a comment - The horizontal line (-----) after the startup message is part of the shutdown message. Is the blank line needed at all? I'd assume the horizontal line would be a good enough visual separator.
          Hide
          Kim Haase added a comment -

          Yes, that would be an acceptable change for the log.

          I don't know if the horizontal line after "Database Class Loader started" is part of the startup message or part of the shutdown message, because it didn't exist at all previously. It would be fine if it were moved down so that the output looked like this:

          ---------------------------------------------------------------
          Wed Oct 20 17:14:46 EDT 2010:
          Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alpha - (1025709): instance a816c00e-012b-cb7e-7d07-000000bb7e18
          on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e
          Loaded from file:/export/home/chaase/javadbmore/codetrunk/trunk/jars/insane/derby.jar
          java.vendor=Sun Microsystems Inc.
          java.runtime.version=1.6.0_21-b06
          Database Class Loader started - derby.database.classpath=''

          ----------------------------------------------------------------
          Wed Oct 20 17:15:37 EDT 2010: Shutting down Derby engine
          ----------------------------------------------------------------
          Wed Oct 20 17:15:37 EDT 2010:
          Shutting down instance a816c00e-012b-cb7e-7d07-000000bb7e18 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e
          ----------------------------------------------------------------

          It depends on what is easier for you to do.

          Show
          Kim Haase added a comment - Yes, that would be an acceptable change for the log. I don't know if the horizontal line after "Database Class Loader started" is part of the startup message or part of the shutdown message, because it didn't exist at all previously. It would be fine if it were moved down so that the output looked like this: --------------------------------------------------------------- Wed Oct 20 17:14:46 EDT 2010: Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alpha - (1025709): instance a816c00e-012b-cb7e-7d07-000000bb7e18 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e Loaded from file:/export/home/chaase/javadbmore/codetrunk/trunk/jars/insane/derby.jar java.vendor=Sun Microsystems Inc. java.runtime.version=1.6.0_21-b06 Database Class Loader started - derby.database.classpath='' ---------------------------------------------------------------- Wed Oct 20 17:15:37 EDT 2010: Shutting down Derby engine ---------------------------------------------------------------- Wed Oct 20 17:15:37 EDT 2010: Shutting down instance a816c00e-012b-cb7e-7d07-000000bb7e18 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e ---------------------------------------------------------------- It depends on what is easier for you to do.
          Hide
          Mamta A. Satoor added a comment -

          Kim, just want to make sure that I understood your suggestion right. You mean the log in your comment above should read like following?

          ----------------------------------------------------------------
          Wed Oct 20 17:14:46 EDT 2010:
          Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alpha - (1025709): instance a816c00e-012b-cb7e-7d07-000000bb7e18
          on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e
          Loaded from file:/export/home/chaase/javadbmore/codetrunk/trunk/jars/insane/derby.jar
          java.vendor=Sun Microsystems Inc.
          java.runtime.version=1.6.0_21-b06
          Database Class Loader started - derby.database.classpath=''
          ----------------------------------------------------------------

          Wed Oct 20 17:15:37 EDT 2010: Shutting down Derby engine
          ----------------------------------------------------------------
          Wed Oct 20 17:15:37 EDT 2010:
          Shutting down instance a816c00e-012b-cb7e-7d07-000000bb7e18 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e
          ----------------------------------------------------------------

          Show
          Mamta A. Satoor added a comment - Kim, just want to make sure that I understood your suggestion right. You mean the log in your comment above should read like following? ---------------------------------------------------------------- Wed Oct 20 17:14:46 EDT 2010: Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alpha - (1025709): instance a816c00e-012b-cb7e-7d07-000000bb7e18 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e Loaded from file:/export/home/chaase/javadbmore/codetrunk/trunk/jars/insane/derby.jar java.vendor=Sun Microsystems Inc. java.runtime.version=1.6.0_21-b06 Database Class Loader started - derby.database.classpath='' ---------------------------------------------------------------- Wed Oct 20 17:15:37 EDT 2010: Shutting down Derby engine ---------------------------------------------------------------- Wed Oct 20 17:15:37 EDT 2010: Shutting down instance a816c00e-012b-cb7e-7d07-000000bb7e18 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e ----------------------------------------------------------------
          Hide
          Kim Haase added a comment -

          The colons look perfect now with this fix, and the spelling of "engine".

          However, the line break does not seem to be in the right place. It seems to be in the middle of the shutdown messages, not at the beginning. This is the output I see in the log:

          ----------------------------------------------------------------
          Wed Oct 20 17:14:46 EDT 2010:
          Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alpha - (1025709): instance a816c00e-012b-cb7e-7d07-000000bb7e18
          on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e
          Loaded from file:/export/home/chaase/javadbmore/codetrunk/trunk/jars/insane/derby.jar
          java.vendor=Sun Microsystems Inc.
          java.runtime.version=1.6.0_21-b06
          Database Class Loader started - derby.database.classpath=''
          ----------------------------------------------------------------
          Wed Oct 20 17:15:37 EDT 2010: Shutting down Derby engine
          ----------------------------------------------------------------

          Wed Oct 20 17:15:37 EDT 2010:
          Shutting down instance a816c00e-012b-cb7e-7d07-000000bb7e18 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e
          ----------------------------------------------------------------

          I was expecting the space to be after the "Database Class Loader started" line – not between the two "Shutting down" messages. Can this be fixed?

          Show
          Kim Haase added a comment - The colons look perfect now with this fix, and the spelling of "engine". However, the line break does not seem to be in the right place. It seems to be in the middle of the shutdown messages, not at the beginning. This is the output I see in the log: ---------------------------------------------------------------- Wed Oct 20 17:14:46 EDT 2010: Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alpha - (1025709): instance a816c00e-012b-cb7e-7d07-000000bb7e18 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e Loaded from file:/export/home/chaase/javadbmore/codetrunk/trunk/jars/insane/derby.jar java.vendor=Sun Microsystems Inc. java.runtime.version=1.6.0_21-b06 Database Class Loader started - derby.database.classpath='' ---------------------------------------------------------------- Wed Oct 20 17:15:37 EDT 2010: Shutting down Derby engine ---------------------------------------------------------------- Wed Oct 20 17:15:37 EDT 2010: Shutting down instance a816c00e-012b-cb7e-7d07-000000bb7e18 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e ---------------------------------------------------------------- I was expecting the space to be after the "Database Class Loader started" line – not between the two "Shutting down" messages. Can this be fixed?
          Hide
          Mamta A. Satoor added a comment -

          I changed the message to have lower case engine.

          also, I didn't put spaces around the colon with my checkins last night because other existing messages about engine startup and inidividual db shutdowns do not have spaces around the colon. But if having the spaces around the : for shutting down Derby engine makes it easier to read, I have no problems with that at all.

          Show
          Mamta A. Satoor added a comment - I changed the message to have lower case engine. also, I didn't put spaces around the colon with my checkins last night because other existing messages about engine startup and inidividual db shutdowns do not have spaces around the colon. But if having the spaces around the : for shutting down Derby engine makes it easier to read, I have no problems with that at all.
          Hide
          Kim Haase added a comment -

          Thanks very much for fixing the colon, Knut.

          In the documentation we never capitalize "engine" in "Derby engine", so that's a good catch – it should not be capitalized.

          Show
          Kim Haase added a comment - Thanks very much for fixing the colon, Knut. In the documentation we never capitalize "engine" in "Derby engine", so that's a good catch – it should not be capitalized.
          Hide
          Knut Anders Hatlen added a comment -

          By the way, is the word "Engine" in "Shutting down Derby Engine" supposed to be capitalized, or should it be changed to lowercase?

          Show
          Knut Anders Hatlen added a comment - By the way, is the word "Engine" in "Shutting down Derby Engine" supposed to be capitalized, or should it be changed to lowercase?
          Hide
          Knut Anders Hatlen added a comment - - edited

          I think the lacking space Kim referred to was in the shutdown engine message, which looks like this in the attached derby.log:

          Tue Oct 19 22:52:03 PDT 2010:Shutting down Derby Engine

          I agree with Kim that there should be a space between the colon and "Shutting", so I took the liberty of checking in the attached patch "space.diff". The message now looks like this:

          Wed Oct 20 12:29:03 CEST 2010: Shutting down Derby Engine

          Committed revision 1025498.

          Show
          Knut Anders Hatlen added a comment - - edited I think the lacking space Kim referred to was in the shutdown engine message, which looks like this in the attached derby.log: Tue Oct 19 22:52:03 PDT 2010:Shutting down Derby Engine I agree with Kim that there should be a space between the colon and "Shutting", so I took the liberty of checking in the attached patch "space.diff". The message now looks like this: Wed Oct 20 12:29:03 CEST 2010: Shutting down Derby Engine Committed revision 1025498.
          Hide
          Mamta A. Satoor added a comment -

          Kim, I made couple checkins to make the log file more readable. Now, there will be a line break between the startup and shutdown messages. And there will be no space around the : which will match the format for the startup message. Eg of derby.log is attached to this jira.

          Show
          Mamta A. Satoor added a comment - Kim, I made couple checkins to make the log file more readable. Now, there will be a line break between the startup and shutdown messages. And there will be no space around the : which will match the format for the startup message. Eg of derby.log is attached to this jira.
          Hide
          Kim Haase added a comment -

          Thanks, Mamta, for those answers.

          I think it will indeed be helpful to users if you can restore the line break between the startup and shutdown messages. Hope it's not a nuisance to do this.

          About the shutdown message – Is there a way to put a space after the colon, to make the punctuation correct at least?

          ": Shutting"

          instead of

          ":Shutting"

          Thanks.

          Show
          Kim Haase added a comment - Thanks, Mamta, for those answers. I think it will indeed be helpful to users if you can restore the line break between the startup and shutdown messages. Hope it's not a nuisance to do this. About the shutdown message – Is there a way to put a space after the colon, to make the punctuation correct at least? ": Shutting" instead of ":Shutting" Thanks.
          Hide
          Mamta A. Satoor added a comment -

          Kim, thanks for looking at the doc side of the issue. To answer your three questions
          1)The date format is easier to read.
          How we print the date information in the log file was intentionally changed as part of DERBY-4752(CheapDateFormatter returns incorrect and invalid date strings).
          2)There is no line break between the startup and shutdown messages – there used to be.
          You are correct about this. I can spend more time on this if it will make the log file easier to read.
          3)The shutdown message is on two lines, not one.
          The shutdown message now includes the database name and because of that additional information, it overflows on two lines rather than one line.

          Show
          Mamta A. Satoor added a comment - Kim, thanks for looking at the doc side of the issue. To answer your three questions 1)The date format is easier to read. How we print the date information in the log file was intentionally changed as part of DERBY-4752 (CheapDateFormatter returns incorrect and invalid date strings). 2)There is no line break between the startup and shutdown messages – there used to be. You are correct about this. I can spend more time on this if it will make the log file easier to read. 3)The shutdown message is on two lines, not one. The shutdown message now includes the database name and because of that additional information, it overflows on two lines rather than one line.
          Hide
          Kim Haase added a comment -

          Just as a sanity check – I see something a little different:

          • The date format is easier to read.
          • There is no line break between the startup and shutdown messages – there used to be.
          • The shutdown message is on two lines, not one.

          Is this all correct?

          ----------------------------------------------------------------
          Thu Sep 30 17:00:17 EDT 2010:
          Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alpha - (1003243): instance a816c00e-012b-6472-09bc-000000bb5af0
          on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e
          Loaded from file:/export/home/chaase/javadbmore/codetrunk/trunk/jars/insane/derby.jar
          java.vendor=Sun Microsystems Inc.
          java.runtime.version=1.6.0_21-b06
          Database Class Loader started - derby.database.classpath=''
          Thu Sep 30 17:03:21 EDT 2010 Thread[main,5,main]
          :Shutting down Derby Engine
          ----------------------------------------------------------------

          Thu Sep 30 17:03:21 EDT 2010:
          Shutting down instance a816c00e-012b-6472-09bc-000000bb5af0 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e
          ----------------------------------------------------------------

          Show
          Kim Haase added a comment - Just as a sanity check – I see something a little different: The date format is easier to read. There is no line break between the startup and shutdown messages – there used to be. The shutdown message is on two lines, not one. Is this all correct? ---------------------------------------------------------------- Thu Sep 30 17:00:17 EDT 2010: Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alpha - (1003243): instance a816c00e-012b-6472-09bc-000000bb5af0 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e Loaded from file:/export/home/chaase/javadbmore/codetrunk/trunk/jars/insane/derby.jar java.vendor=Sun Microsystems Inc. java.runtime.version=1.6.0_21-b06 Database Class Loader started - derby.database.classpath='' Thu Sep 30 17:03:21 EDT 2010 Thread [main,5,main] :Shutting down Derby Engine ---------------------------------------------------------------- Thu Sep 30 17:03:21 EDT 2010: Shutting down instance a816c00e-012b-6472-09bc-000000bb5af0 on database directory /export/home/chaase/DERBYTUTOR/firstdb with class loader sun.misc.Launcher$AppClassLoader@7d772e ----------------------------------------------------------------
          Hide
          Kim Haase added a comment -

          Thanks for pointing this out. This will need to be part of the documentation cleanup we do at a new release of Derby (just filed as DERBY-4826). I'll create a link between these two issues.

          Show
          Kim Haase added a comment - Thanks for pointing this out. This will need to be part of the documentation cleanup we do at a new release of Derby (just filed as DERBY-4826 ). I'll create a link between these two issues.
          Hide
          Lily Wei added a comment -

          Thanks to Kim. DERBY-4715 documentation change reflects here:
          DERBY-4715 added a new message to derby.log during engine boot for derby.jar
          file location and jvm information. Need to update docs with that information. As DERBY-
          4601, 2 places in Derby's docs where we show examples of boot messages
          1)In Getting started Guide, under Creating a Derby database and running SQL statements
          section, we show a typical startup and shutdown message. That section will need to change
          2)In Derby Developer's Guide, under section Derby System -> Booting databases

          An eg of engine boot message in derby.log is:
          2010-07-21 18:43:02.968 GMT:
          Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alpha - (978803): instance a816c00e-0129-f650-e20c-000000c1b4f8
          on database directory C:\derby\trunk\testtmp\test with class loader sun.misc.Launcher$AppClasLoader@11b86e7
          Loaded from file:/C:/derby/trunk/jars/sane/derby.jar
          java.vendor=Sun Microsystems Inc.
          java.runtime.version=1.6.0_20-b02
          Database Class Loader started - derby.database.classpath=''

          Show
          Lily Wei added a comment - Thanks to Kim. DERBY-4715 documentation change reflects here: DERBY-4715 added a new message to derby.log during engine boot for derby.jar file location and jvm information. Need to update docs with that information. As DERBY- 4601, 2 places in Derby's docs where we show examples of boot messages 1)In Getting started Guide, under Creating a Derby database and running SQL statements section, we show a typical startup and shutdown message. That section will need to change 2)In Derby Developer's Guide, under section Derby System -> Booting databases An eg of engine boot message in derby.log is: 2010-07-21 18:43:02.968 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alpha - (978803): instance a816c00e-0129-f650-e20c-000000c1b4f8 on database directory C:\derby\trunk\testtmp\test with class loader sun.misc.Launcher$AppClasLoader@11b86e7 Loaded from file:/C:/derby/trunk/jars/sane/derby.jar java.vendor=Sun Microsystems Inc. java.runtime.version=1.6.0_20-b02 Database Class Loader started - derby.database.classpath=''

            People

            • Assignee:
              Kim Haase
              Reporter:
              Mamta A. Satoor
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development