Derby
  1. Derby
  2. DERBY-5514

SecureServerTest (and others) don't play nice with EMMA: AccessControlException

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.9.1.0
    • Fix Version/s: 10.9.1.0
    • Component/s: Test
    • Labels:
      None

      Description

      When running SecureServerTest with jars instrumented with EMMA using the ant emma-all target, I see:

      [junit] (net)derbynet.SecureServerTest.testServerStartup used 8475 ms junit.framework.TestListener: endTest(testServerStartup)
      [junit] START-SPAWNED:SpawnedNetworkServer ERROR OUTPUT:
      [junit] java.security.policy: error adding Entry:
      [junit] java.net.MalformedURLException: no protocol: /export/home/dag/java/sb/sb1/tools/java/emma.jar
      [junit] java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
      [junit] at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
      [junit] at java.security.AccessController.checkPermission(AccessController.java:546)
      [junit] at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
      [junit] at java.lang.SecurityManager.checkRead(SecurityManager.java:871)
      [junit] at java.io.File.exists(File.java:731)
      [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:525)
      [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:86)
      [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:54)
      [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
      [junit] at java.lang.Thread.run(Thread.java:662)
      [junit] Exception in thread "EMMA shutdown handler thread" java.lang.RuntimeException: EMMA failed to dump coverage data: java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
      [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:71)
      [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
      [junit] at java.lang.Thread.run(Thread.java:662)
      [junit] END-SPAWNED :SpawnedNetworkServer ERROR OUTPUT:

      This is presumably because the test spawns a server which runs with the default server policy.

      Another thing is that is seems dangerous to let the spawned process write to EMMA's "coverage.ec", since we don't know when the parent process will write to it. This behavior could be what's been causing our corrutions in the EMMA runs earlier. The missing permissions just highlight what's happening.

      In this case the spawned process was started with this command line (I instrumented the code):

      XXX server startup command = /usr/jdk/instances/jdk1.6.0/jre/bin/java -classpath /<my sandbox>/tools/java/emma.jar:/<my sandbox>/jars/sane/derbyTesting.jar:/<my sandbox>/jars/emma/lib/derbyclient.jar:/<my sandbox>/jars/emma/lib/derbynet.jar:/<my sandbox>/jars/emma/lib/derby.jar:/<my sandbox>/jars/emma/lib/derbytools.jar:/<my sandbox>/jars/emma/lib/derbyrun.jar:/<my sandbox>/tools/java/junit.jar:/usr/share/lib/ant/ant-launcher.jar:/usr/share/lib/ant/ant.jar:/usr/share/lib/ant/ant-junit.jar org.apache.derby.drda.NetworkServerControl start -h localhost -p 1527

      Possible approaches:
      run the spawned VMs with plain jars (downside: we won't get coverage for those)
      run the spawned with a special default policy file when we run with EMMA ++
      run the spawned VM with -noSecurityManager if with EMMA jars

      1. d5514-emma-permissions-to-all.diff
        30 kB
        Knut Anders Hatlen
      2. derby-5514-1.diff
        2 kB
        Dag H. Wanvik
      3. derby-5514-1.stat
        0.2 kB
        Dag H. Wanvik
      4. derby-5514-2.diff
        4 kB
        Dag H. Wanvik
      5. derby-5514-2.stat
        0.3 kB
        Dag H. Wanvik

        Issue Links

          Activity

          Dag H. Wanvik created issue -
          Dag H. Wanvik made changes -
          Field Original Value New Value
          Description When running SecureServerTest with jars instrumented with EMMA using the ant emma-all target, I see:

          [junit] (net)derbynet.SecureServerTest.testServerStartup used 8475 ms junit.framework.TestListener: endTest(testServerStartup)
              [junit] START-SPAWNED:SpawnedNetworkServer ERROR OUTPUT:
              [junit] java.security.policy: error adding Entry:
              [junit] java.net.MalformedURLException: no protocol: /export/home/dag/java/sb/sb1/tools/java/emma.jar
              [junit] java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
              [junit] at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
              [junit] at java.security.AccessController.checkPermission(AccessController.java:546)
              [junit] at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
              [junit] at java.lang.SecurityManager.checkRead(SecurityManager.java:871)
              [junit] at java.io.File.exists(File.java:731)
              [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:525)
              [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:86)
              [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:54)
              [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
              [junit] at java.lang.Thread.run(Thread.java:662)
              [junit] Exception in thread "EMMA shutdown handler thread" java.lang.RuntimeException: EMMA failed to dump coverage data: java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
              [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:71)
              [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
              [junit] at java.lang.Thread.run(Thread.java:662)
              [junit] END-SPAWNED :SpawnedNetworkServer ERROR OUTPUT:

          This is presumably because the test spawns a server which runs with the default server policy.

          Another thing is that is seems dangerous to let the spawned process write to EMMA's "coverage.ec", since we don't know when the parent process will write to it. This behavior could be what's been causing our corrutions in the EMMA runs earlier. The missing permissions just highlight what's happening.

          In this case the spawned process was started with this command line (I instrumented the code):

          XXX server startup command = /usr/jdk/instances/jdk1.6.0/jre/bin/java -classpath /<my sandbox>/tools/java/emma.jar:/<my sandbox>/jars/sane/derbyTesting.jar:/<my sandbox>/jars/emma/lib/derbyclient.jar:/<my sandbox>/jars/emma/lib/derbynet.jar:/<my sandbox>/jars/emma/lib/derby.jar:/<my sandbox>/jars/emma/lib/derbytools.jar:/<my sandbox>/jars/emma/lib/derbyrun.jar:/<my sandbox>/tools/java/junit.jar:/usr/share/lib/ant/ant-launcher.jar:/usr/share/lib/ant/ant.jar:/usr/share/lib/ant/ant-junit.jar org.apache.derby.drda.NetworkServerControl start -h localhost -p 1527

          Possible approaches:
                   run inferior VMs with plain jars (downside: we won't get coverage for those)
                   run with a special default policy file when we run with EMMA, detect when we fork
                   with EMMA jars and use a dedicated "coverage.ec", either by telling EMMA to use another one if possible,
                   
          When running SecureServerTest with jars instrumented with EMMA using the ant emma-all target, I see:

          [junit] (net)derbynet.SecureServerTest.testServerStartup used 8475 ms junit.framework.TestListener: endTest(testServerStartup)
              [junit] START-SPAWNED:SpawnedNetworkServer ERROR OUTPUT:
              [junit] java.security.policy: error adding Entry:
              [junit] java.net.MalformedURLException: no protocol: /export/home/dag/java/sb/sb1/tools/java/emma.jar
              [junit] java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
              [junit] at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
              [junit] at java.security.AccessController.checkPermission(AccessController.java:546)
              [junit] at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
              [junit] at java.lang.SecurityManager.checkRead(SecurityManager.java:871)
              [junit] at java.io.File.exists(File.java:731)
              [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:525)
              [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:86)
              [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:54)
              [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
              [junit] at java.lang.Thread.run(Thread.java:662)
              [junit] Exception in thread "EMMA shutdown handler thread" java.lang.RuntimeException: EMMA failed to dump coverage data: java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
              [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:71)
              [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
              [junit] at java.lang.Thread.run(Thread.java:662)
              [junit] END-SPAWNED :SpawnedNetworkServer ERROR OUTPUT:

          This is presumably because the test spawns a server which runs with the default server policy.

          Another thing is that is seems dangerous to let the spawned process write to EMMA's "coverage.ec", since we don't know when the parent process will write to it. This behavior could be what's been causing our corrutions in the EMMA runs earlier. The missing permissions just highlight what's happening.

          In this case the spawned process was started with this command line (I instrumented the code):

          XXX server startup command = /usr/jdk/instances/jdk1.6.0/jre/bin/java -classpath /<my sandbox>/tools/java/emma.jar:/<my sandbox>/jars/sane/derbyTesting.jar:/<my sandbox>/jars/emma/lib/derbyclient.jar:/<my sandbox>/jars/emma/lib/derbynet.jar:/<my sandbox>/jars/emma/lib/derby.jar:/<my sandbox>/jars/emma/lib/derbytools.jar:/<my sandbox>/jars/emma/lib/derbyrun.jar:/<my sandbox>/tools/java/junit.jar:/usr/share/lib/ant/ant-launcher.jar:/usr/share/lib/ant/ant.jar:/usr/share/lib/ant/ant-junit.jar org.apache.derby.drda.NetworkServerControl start -h localhost -p 1527

          Possible approaches:
                   run inferior VMs with plain jars (downside: we won't get coverage for those)
                   run with a special default policy file when we run with EMMA ++
                   
          Dag H. Wanvik made changes -
          Description When running SecureServerTest with jars instrumented with EMMA using the ant emma-all target, I see:

          [junit] (net)derbynet.SecureServerTest.testServerStartup used 8475 ms junit.framework.TestListener: endTest(testServerStartup)
              [junit] START-SPAWNED:SpawnedNetworkServer ERROR OUTPUT:
              [junit] java.security.policy: error adding Entry:
              [junit] java.net.MalformedURLException: no protocol: /export/home/dag/java/sb/sb1/tools/java/emma.jar
              [junit] java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
              [junit] at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
              [junit] at java.security.AccessController.checkPermission(AccessController.java:546)
              [junit] at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
              [junit] at java.lang.SecurityManager.checkRead(SecurityManager.java:871)
              [junit] at java.io.File.exists(File.java:731)
              [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:525)
              [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:86)
              [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:54)
              [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
              [junit] at java.lang.Thread.run(Thread.java:662)
              [junit] Exception in thread "EMMA shutdown handler thread" java.lang.RuntimeException: EMMA failed to dump coverage data: java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
              [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:71)
              [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
              [junit] at java.lang.Thread.run(Thread.java:662)
              [junit] END-SPAWNED :SpawnedNetworkServer ERROR OUTPUT:

          This is presumably because the test spawns a server which runs with the default server policy.

          Another thing is that is seems dangerous to let the spawned process write to EMMA's "coverage.ec", since we don't know when the parent process will write to it. This behavior could be what's been causing our corrutions in the EMMA runs earlier. The missing permissions just highlight what's happening.

          In this case the spawned process was started with this command line (I instrumented the code):

          XXX server startup command = /usr/jdk/instances/jdk1.6.0/jre/bin/java -classpath /<my sandbox>/tools/java/emma.jar:/<my sandbox>/jars/sane/derbyTesting.jar:/<my sandbox>/jars/emma/lib/derbyclient.jar:/<my sandbox>/jars/emma/lib/derbynet.jar:/<my sandbox>/jars/emma/lib/derby.jar:/<my sandbox>/jars/emma/lib/derbytools.jar:/<my sandbox>/jars/emma/lib/derbyrun.jar:/<my sandbox>/tools/java/junit.jar:/usr/share/lib/ant/ant-launcher.jar:/usr/share/lib/ant/ant.jar:/usr/share/lib/ant/ant-junit.jar org.apache.derby.drda.NetworkServerControl start -h localhost -p 1527

          Possible approaches:
                   run inferior VMs with plain jars (downside: we won't get coverage for those)
                   run with a special default policy file when we run with EMMA ++
                   
          When running SecureServerTest with jars instrumented with EMMA using the ant emma-all target, I see:

          [junit] (net)derbynet.SecureServerTest.testServerStartup used 8475 ms junit.framework.TestListener: endTest(testServerStartup)
              [junit] START-SPAWNED:SpawnedNetworkServer ERROR OUTPUT:
              [junit] java.security.policy: error adding Entry:
              [junit] java.net.MalformedURLException: no protocol: /export/home/dag/java/sb/sb1/tools/java/emma.jar
              [junit] java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
              [junit] at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
              [junit] at java.security.AccessController.checkPermission(AccessController.java:546)
              [junit] at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
              [junit] at java.lang.SecurityManager.checkRead(SecurityManager.java:871)
              [junit] at java.io.File.exists(File.java:731)
              [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:525)
              [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:86)
              [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:54)
              [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
              [junit] at java.lang.Thread.run(Thread.java:662)
              [junit] Exception in thread "EMMA shutdown handler thread" java.lang.RuntimeException: EMMA failed to dump coverage data: java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
              [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:71)
              [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
              [junit] at java.lang.Thread.run(Thread.java:662)
              [junit] END-SPAWNED :SpawnedNetworkServer ERROR OUTPUT:

          This is presumably because the test spawns a server which runs with the default server policy.

          Another thing is that is seems dangerous to let the spawned process write to EMMA's "coverage.ec", since we don't know when the parent process will write to it. This behavior could be what's been causing our corrutions in the EMMA runs earlier. The missing permissions just highlight what's happening.

          In this case the spawned process was started with this command line (I instrumented the code):

          XXX server startup command = /usr/jdk/instances/jdk1.6.0/jre/bin/java -classpath /<my sandbox>/tools/java/emma.jar:/<my sandbox>/jars/sane/derbyTesting.jar:/<my sandbox>/jars/emma/lib/derbyclient.jar:/<my sandbox>/jars/emma/lib/derbynet.jar:/<my sandbox>/jars/emma/lib/derby.jar:/<my sandbox>/jars/emma/lib/derbytools.jar:/<my sandbox>/jars/emma/lib/derbyrun.jar:/<my sandbox>/tools/java/junit.jar:/usr/share/lib/ant/ant-launcher.jar:/usr/share/lib/ant/ant.jar:/usr/share/lib/ant/ant-junit.jar org.apache.derby.drda.NetworkServerControl start -h localhost -p 1527

          Possible approaches:
                   run inferior VMs with plain jars (downside: we won't get coverage for those)
                   run with a special default policy file when we run with EMMA ++
                   run the spawned VM with -noSecurityManager if with EMMA jars
          Dag H. Wanvik made changes -
          Summary SecureServerTest doesn't play nice ewith EMMA: AccessControlException SecureServerTest doesn't play nice with EMMA: AccessControlException
          Description When running SecureServerTest with jars instrumented with EMMA using the ant emma-all target, I see:

          [junit] (net)derbynet.SecureServerTest.testServerStartup used 8475 ms junit.framework.TestListener: endTest(testServerStartup)
              [junit] START-SPAWNED:SpawnedNetworkServer ERROR OUTPUT:
              [junit] java.security.policy: error adding Entry:
              [junit] java.net.MalformedURLException: no protocol: /export/home/dag/java/sb/sb1/tools/java/emma.jar
              [junit] java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
              [junit] at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
              [junit] at java.security.AccessController.checkPermission(AccessController.java:546)
              [junit] at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
              [junit] at java.lang.SecurityManager.checkRead(SecurityManager.java:871)
              [junit] at java.io.File.exists(File.java:731)
              [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:525)
              [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:86)
              [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:54)
              [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
              [junit] at java.lang.Thread.run(Thread.java:662)
              [junit] Exception in thread "EMMA shutdown handler thread" java.lang.RuntimeException: EMMA failed to dump coverage data: java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
              [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:71)
              [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
              [junit] at java.lang.Thread.run(Thread.java:662)
              [junit] END-SPAWNED :SpawnedNetworkServer ERROR OUTPUT:

          This is presumably because the test spawns a server which runs with the default server policy.

          Another thing is that is seems dangerous to let the spawned process write to EMMA's "coverage.ec", since we don't know when the parent process will write to it. This behavior could be what's been causing our corrutions in the EMMA runs earlier. The missing permissions just highlight what's happening.

          In this case the spawned process was started with this command line (I instrumented the code):

          XXX server startup command = /usr/jdk/instances/jdk1.6.0/jre/bin/java -classpath /<my sandbox>/tools/java/emma.jar:/<my sandbox>/jars/sane/derbyTesting.jar:/<my sandbox>/jars/emma/lib/derbyclient.jar:/<my sandbox>/jars/emma/lib/derbynet.jar:/<my sandbox>/jars/emma/lib/derby.jar:/<my sandbox>/jars/emma/lib/derbytools.jar:/<my sandbox>/jars/emma/lib/derbyrun.jar:/<my sandbox>/tools/java/junit.jar:/usr/share/lib/ant/ant-launcher.jar:/usr/share/lib/ant/ant.jar:/usr/share/lib/ant/ant-junit.jar org.apache.derby.drda.NetworkServerControl start -h localhost -p 1527

          Possible approaches:
                   run inferior VMs with plain jars (downside: we won't get coverage for those)
                   run with a special default policy file when we run with EMMA ++
                   run the spawned VM with -noSecurityManager if with EMMA jars
          When running SecureServerTest with jars instrumented with EMMA using the ant emma-all target, I see:

          [junit] (net)derbynet.SecureServerTest.testServerStartup used 8475 ms junit.framework.TestListener: endTest(testServerStartup)
              [junit] START-SPAWNED:SpawnedNetworkServer ERROR OUTPUT:
              [junit] java.security.policy: error adding Entry:
              [junit] java.net.MalformedURLException: no protocol: /export/home/dag/java/sb/sb1/tools/java/emma.jar
              [junit] java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
              [junit] at java.security.AccessControlContext.checkPermission(AccessControlContext.java:374)
              [junit] at java.security.AccessController.checkPermission(AccessController.java:546)
              [junit] at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
              [junit] at java.lang.SecurityManager.checkRead(SecurityManager.java:871)
              [junit] at java.io.File.exists(File.java:731)
              [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:525)
              [junit] at com.vladium.emma.data.DataFactory.persist(DataFactory.java:86)
              [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:54)
              [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
              [junit] at java.lang.Thread.run(Thread.java:662)
              [junit] Exception in thread "EMMA shutdown handler thread" java.lang.RuntimeException: EMMA failed to dump coverage data: java.security.AccessControlException: access denied (java.io.FilePermission coverage.ec read)
              [junit] at com.vladium.emma.rt.RTCoverageDataPersister.dumpCoverageData(RTCoverageDataPersister.java:71)
              [junit] at com.vladium.emma.rt.RTExitHook.run(RTExitHook.java:32)
              [junit] at java.lang.Thread.run(Thread.java:662)
              [junit] END-SPAWNED :SpawnedNetworkServer ERROR OUTPUT:

          This is presumably because the test spawns a server which runs with the default server policy.

          Another thing is that is seems dangerous to let the spawned process write to EMMA's "coverage.ec", since we don't know when the parent process will write to it. This behavior could be what's been causing our corrutions in the EMMA runs earlier. The missing permissions just highlight what's happening.

          In this case the spawned process was started with this command line (I instrumented the code):

          XXX server startup command = /usr/jdk/instances/jdk1.6.0/jre/bin/java -classpath /<my sandbox>/tools/java/emma.jar:/<my sandbox>/jars/sane/derbyTesting.jar:/<my sandbox>/jars/emma/lib/derbyclient.jar:/<my sandbox>/jars/emma/lib/derbynet.jar:/<my sandbox>/jars/emma/lib/derby.jar:/<my sandbox>/jars/emma/lib/derbytools.jar:/<my sandbox>/jars/emma/lib/derbyrun.jar:/<my sandbox>/tools/java/junit.jar:/usr/share/lib/ant/ant-launcher.jar:/usr/share/lib/ant/ant.jar:/usr/share/lib/ant/ant-junit.jar org.apache.derby.drda.NetworkServerControl start -h localhost -p 1527

          Possible approaches:
                   run the spawned VMs with plain jars (downside: we won't get coverage for those)
                   run the spawned with a special default policy file when we run with EMMA ++
                   run the spawned VM with -noSecurityManager if with EMMA jars
          Dag H. Wanvik made changes -
          Attachment derby-5514-1.diff [ 12504958 ]
          Attachment derby-5514-1.stat [ 12504959 ]
          Dag H. Wanvik made changes -
          Issue & fix info Patch Available [ 10102 ]
          Dag H. Wanvik made changes -
          Summary SecureServerTest doesn't play nice with EMMA: AccessControlException SecureServerTest (and others) don't play nice with EMMA: AccessControlException
          Knut Anders Hatlen made changes -
          Attachment d5514-emma-permissions-to-all.diff [ 12505099 ]
          Dag H. Wanvik made changes -
          Attachment derby-5514-2.diff [ 12505164 ]
          Attachment derby-5514-2.stat [ 12505165 ]
          Dag H. Wanvik made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Issue & fix info Patch Available [ 10102 ]
          Fix Version/s 10.9.0.0 [ 12316344 ]
          Resolution Fixed [ 1 ]
          Dag H. Wanvik made changes -
          Component/s Test [ 11413 ]
          Dag H. Wanvik made changes -
          Assignee Dag H. Wanvik [ dagw ]
          Knut Anders Hatlen made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          Gavin made changes -
          Workflow jira [ 12643268 ] Default workflow, editable Closed status [ 12802701 ]
          Knut Anders Hatlen made changes -
          Link This issue duplicates DERBY-3647 [ DERBY-3647 ]

            People

            • Assignee:
              Dag H. Wanvik
              Reporter:
              Dag H. Wanvik
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development