[ 
https://issues.apache.org/jira/browse/SOLR-14100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997647#comment-16997647
 ] 

Robert Muir commented on SOLR-14100:
------------------------------------

That's a bug: look at the spelling :)
{noformat}
at java.base/java.lang.Thread.run(Thread.java:830)Throwable #3: 
java.security.AccessControlException: access denied 
("java.util.PropertyPermission" "solr.zkclienttmeout" "write")
   [junit4]    >        at 
__randomizedtesting.SeedInfo.seed([CABF02A0448E53CF]:0)
   [junit4]    >        at 
java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
   [junit4]    >        at 
java.base/java.security.AccessController.checkPermission(AccessController.java:1036)
   [junit4]    >        at 
java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:408)
   [junit4]    >        at 
java.base/java.lang.System.clearProperty(System.java:968)
   [junit4]    >        at 
org.apache.solr.SolrTestCaseJ4.teardownTestCases(SolrTestCaseJ4.java:350)
{noformat}

> System properties cross test suite boundary
> -------------------------------------------
>
>                 Key: SOLR-14100
>                 URL: https://issues.apache.org/jira/browse/SOLR-14100
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Dawid Weiss
>            Assignee: Dawid Weiss
>            Priority: Major
>
> At some point in time all system properties were saved/ restored in the top 
> test class. When security manager was added (a long time ago) as the default 
> this has been turned off (because the rule couldn't read all properties then) 
> and replaced with just a selected subset of properties to be checked (in 
> LuceneTestCase). Sadly, Solr's security policy allows all properties to be 
> written and I bet this also leads to complex interactions between tests.
> We can allow read access to all properties at first but all writeable/ 
> modifiable properties should be identified and added to a top-level restore 
> rule, along with security manager policy that selectively enables them (so 
> that we know they're saved and restored after each test).
> This is going to be a tedious task.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to