[
https://issues.apache.org/jira/browse/DERBY-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607330#action_12607330
]
Kathey Marsden commented on DERBY-3708:
---------------------------------------
I think I need part of the fix for DERBY-3504 which fixed the potential for
server hang. One thing I notice is if I abort the test and the server process
is left running I can then ping or shutdown the server. So that lends itself
to it being a problem with processing the output from the process (DERBY-3504).
It doesn't look like a clean merge though. I think I also need some other
intervening change.
> 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.
