db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Reopened: (DERBY-613) Intended location of network server tracing files is not clear.
Date Fri, 21 Oct 2005 00:05:16 GMT
     [ http://issues.apache.org/jira/browse/DERBY-613?page=all ]
Deepa Remesh reopened DERBY-613:

Re-opening to update fix version. This has been merged to 10.1 as revision 327018.

> 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
>     Versions:
>     Reporter: Daniel John Debrunner
>     Assignee: Deepa Remesh
>     Priority: Minor
>      Fix For:

> 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