db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh" <drem...@gmail.com>
Subject Re: [jira] Commented: (DERBY-1845) OutOfMemoryError when running "All" suite directly using JUnit
Date Mon, 09 Oct 2006 16:28:58 GMT
On 10/9/06, Knut Anders Hatlen (JIRA) <derby-dev@db.apache.org> wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-1845?page=comments#action_12440846 ]
> Knut Anders Hatlen commented on DERBY-1845:
> -------------------------------------------
> Is this still a problem after DERBY-1910?

I believe this issue is same as DERBY-1910 and should be resolved now.
However, I have not been able to verify this. When I run the "All"
suite directly using junit, I am getting a new error at the point
where it tries to run the client tests;
1) AllPackagesjava.security.AccessControlException: access denied
(java.io.FilePermission C:\deepa\j
unit_testserverConsoleOutput.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)

I have not seen this error before and wondering if it is caused by
something in my environment. Is anyone else seeing this?


View raw message