db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-613) Intended location of network server tracing files is not clear.
Date Mon, 10 Oct 2005 19:54:48 GMT
Intended location of network server tracing files is not clear.

         Key: DERBY-613
         URL: http://issues.apache.org/jira/browse/DERBY-613
     Project: Derby
        Type: Bug
  Components: Documentation, Network Server  
    Reporter: Daniel John Debrunner
    Priority: Minor

The javadoc for NetworkServer control says:

tracedirectory <tracedirectory> [-h <host>] [-p <portnumber>]: This changes
where new trace files will be placed. For sessions with tracing already turned on, trace files
remain in the previous location. Default is clousdcape.system.home

Apart from the problem of cloudscape.system.home instead of derby.system.home, when I turn
tracing on the trace files are created in the current directory (user.dir) and not derby.system.home.
Also if the documentation is correct, then the location when derby.system.home is not set
should be specified.

java -Dderby.system.home=$PWD/dsh  org.apache.derby.drda.NetworkServerControl  start

Then turn tracing on with

java org.apache.derby.drda.NetworkServerControl  trace on

and connect.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message