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-3110) server hangs after trace on command fails
Date Fri, 26 Oct 2007 18:02:01 GMT

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

Kathey Marsden updated DERBY-3110:

    Attachment: derby-3110_stat.txt

Attached is an initial patch for this issue. If there is an error in turning on tracing for
any of the sessions, we fail to turn global tracing on and return an error to the client.
The change also wraps the tracing in a privilege block   I am working to try to make a test
for this.


> server hangs after trace on command fails
> -----------------------------------------
>                 Key: DERBY-3110
>                 URL: https://issues.apache.org/jira/browse/DERBY-3110
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server
>    Affects Versions:
>            Reporter: Sebb
>            Assignee: Kathey Marsden
>         Attachments: derby-3110_diff.txt, derby-3110_stat.txt
> Tried turning on trace:
> >networkservercontrol  trace on
> Invalid reply from network server: Insufficient data.
> The server process shows the following stack trace:
> access denied (java.io.FilePermission Server58.trace write)
> java.security.AccessControlException: access denied (java.io.FilePermission Server58.trace
>         at java.security.AccessControlContext.checkPermission(AccessControlContext.java:269)
>         at java.security.AccessController.checkPermission(AccessController.java:401)
>         at java.lang.SecurityManager.checkPermission(SecurityManager.java:524)
>         at java.lang.SecurityManager.checkWrite(SecurityManager.java:954)
>         at java.io.FileOutputStream.<init>(FileOutputStream.java:169)
>         at java.io.FileOutputStream.<init>(FileOutputStream.java:70)
>         at java.io.FileWriter.<init>(FileWriter.java:46)
>         at org.apache.derby.impl.drda.DssTrace.startComBufferTrace(Unknown Source)
>         at org.apache.derby.impl.drda.Session.initTrace(Unknown Source)
>         at org.apache.derby.impl.drda.Session.setTraceOn(Unknown Source)
>         at org.apache.derby.impl.drda.NetworkServerControlImpl.setTrace(Unknown Source)
>         at org.apache.derby.impl.drda.NetworkServerControlImpl.processCommands(Unknown
>         at org.apache.derby.impl.drda.DRDAConnThread.sessionInitialState(Unknown Source)
>         at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
> The server now does not respond to ping or shutdown, and has to be killed.
> See also DERBY-3103

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message