db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (DERBY-3647) EMMA is unable to write coverage information from network server when it is started in a separate process with default security policy
Date Mon, 08 Jul 2013 12:37:48 GMT

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

Knut Anders Hatlen closed DERBY-3647.
-------------------------------------

    Resolution: Duplicate

I think this issue was duplicated and fixed by DERBY-5514. Closing.
                
> EMMA is unable to write coverage information from network server when it is started in
a separate process with default security policy
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3647
>                 URL: https://issues.apache.org/jira/browse/DERBY-3647
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.2.2.0
>            Reporter: Vemund Østgaard
>              Labels: derby_triage10_8
>
> This report is based on discussion from DERBY-3445.
> EMMA is unable to write coverage information from network server when it is started in
a separate process with default security policy.
> Exceptions are typically like this:
>     [junit] java.security.AccessControlException: Access denied (java.io.FilePermission
coverage.ec read)
>     [junit] at java.security.AccessController.checkPermission(AccessController.java:104)
>     [junit] at java.lang.SecurityManager.checkPermission(SecurityManager.java:547)
>     [junit] at java.lang.SecurityManager.checkRead(SecurityManager.java:886)
>     [junit] at java.io.File.exists(File.java:726)
>     [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:801)
>     [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:801)
> The discussion in DERBY-3445 suggests a couple of solutions to be able to expand on the
default security policy so that the network server JVM will allow EMMA to write the coverage
data and thus improve the accuracy of the coverage measurements.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message