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 23:13:51 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_test_diff.txt

I am attempting to write a test to test this issue but find that the network server started
in the junit test is acting like it has not been started under security manager.  This test
should fail because
1) It doesn't have the fix for derby-3110 
2) the derby_tests.policy file does not have write permission to derby.system.home

But I find that the trace files are created and no error occurs. Any thoughts on why network
server wouldn't be starting with security manager? I used
 return TestConfiguration.clientServerSuite(NetworkServerControlApiTest.class);

to start network server.

> 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, derby-3110_test_diff.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