[
https://issues.apache.org/jira/browse/DERBY-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608131#action_12608131
]
Kathey Marsden commented on DERBY-3708:
---------------------------------------
I think for the 10.3 fix I will backport the code change but not the test
change and just test manually. I looked into what it would take to backport
the changes to get the spawned process to work properly and not hang and it
looked tangled up with other changes and difficult to backport. Please let me
know if this does not seem acceptable.
> setting tracedirectory from the command line does not work
> ----------------------------------------------------------
>
> Key: DERBY-3708
> URL: https://issues.apache.org/jira/browse/DERBY-3708
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.4.1.4, 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3708_10.3_nocommit.txt, DERBY-3708_diff.txt
>
>
> I tried
> java org.apache.derby.drda.NetworkServerControl tracedirectory /tmp
> and got:
> Trace directory changed to /tmp.
> java org.apache.derby.drda.NetworkServerControl trace on
> Trace turned on for all sessions.
> Trace turned on for all sessions.
> And the trace output was not redirected to the /tmp directory. The
> tracedirectory command seemed to be ignored.
> Setting tracedirectory with the system property derby.drda.traceDirectory or
> with the NetworkServerControl api seems to work ok.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
