db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1951) Missing directory separator in path construction in 'NetworkServerTestSetup.setUp'
Date Tue, 10 Oct 2006 13:55:21 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1951?page=all ]

Kristian Waagan updated DERBY-1951:

    Attachment: derby-1951-1a.diff

'derby-1951-1a.diff' fixes a bug that can be seend depending on the specification of 'derby.system.home'.
If it does not end with a file separator, which is the case if specifed as 'pwd' on Unix system,
an invalid path is constructed for the server log file.

Note that after this patch is applied, other errors and failurs will emerge when running the
'All' JUnit suite (Tests run: 1760,  Failures: 4,  Errors: 3).

Patch is ready for review/commit. I have made the insertion of the file separator unconditional,
in the belief that  multiple file separators will be handled by the JVM/OS. This can easily
be changed if required.

> Missing directory separator in path construction in 'NetworkServerTestSetup.setUp'
> ----------------------------------------------------------------------------------
>                 Key: DERBY-1951
>                 URL: http://issues.apache.org/jira/browse/DERBY-1951
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions:
>            Reporter: Kristian Waagan
>         Assigned To: Kristian Waagan
>         Attachments: derby-1951-1a.diff
> When constructing the path for the server output file, the directory separator (typically
'/') is omitted, causing a security violation when running under the security manager. Here's
a sample stack trace for a JUnit run:
> 1) AllPackagesjava.security.AccessControlException: access denied
> (java.io.FilePermission /some/pathserverConsoleOutput.log write)
>        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 org.apache.derbyTesting.junit.NetworkServerTestSetup$1.run(NetworkServerTestSetup.java:72
> )
>        at java.security.AccessController.doPrivileged(Native Method)
>        at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:65
> )
>        at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
>        at junit.extensions.TestSetup.run(TestSetup.java:23)
>        at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
>        at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
>        at junit.extensions.TestSetup.run(TestSetup.java:23) 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message