db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3708) setting tracedirectory from the command line does not work
Date Mon, 23 Jun 2008 17:40:45 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kathey Marsden updated DERBY-3708:

    Attachment: derby-3708_10.3_nocommit.txt

I merged this fix from 10.4 to 10.3 and am getting a hang in SecureServerTest on Windows only.
It seems to run fine on Linux.  If I look at the processes running I have one for the server
start and another for the ping which seems hung.

If I try to ping the server it just hangs with:
"main" prio=6 tid=0x00297800 nid=0x1eb0 runnable [0x0090f000..0x0090fe54]
   java.lang.Thread.State: RUNNABLE
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:129)
        at java.net.SocketInputStream.read(SocketInputStream.java:90)
        at org.apache.derby.impl.drda.NetworkServerControlImpl.fillReplyBuffer(NetworkServerControlImpl.java:2565)
        at org.apache.derby.impl.drda.NetworkServerControlImpl.readResult(NetworkServerControlImpl.java:2509)
        at org.apache.derby.impl.drda.NetworkServerControlImpl.pingWithNoOpen(NetworkServerControlImpl.java:995)
        at org.apache.derby.impl.drda.NetworkServerControlImpl.ping(NetworkServerControlImpl.java:972)
        at org.apache.derby.impl.drda.NetworkServerControlImpl.executeWork(NetworkServerControlImpl.java:1959)
        at org.apache.derby.drda.NetworkServerControl.main(NetworkServerControl.java:284)

I also get a hang if I try to connect with ij, so the server seems to have stopped accepting

The server is running in a separate process so I don't know how on windows to get a thread
dump for that process.  I've attached the patch derby-3708_10.3_nocommit.txt.  Any thoughts
on how to debug this are welcome.

> 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:,
>            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.

View raw message