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

Noble Paul commented on SOLR-7179:
----------------------------------

I have a property called {{enable.runtime.lib}}
I used initialized it as follows

public static final boolean enableRuntimeLib = 
System.getProperty("enable.runtime.lib","false")

And I do a {{Sytem.setProperty("enable.runtime.lib","true")}} in the 
@BeforeClass method of my test. The test would pass if that is the only test

If I run the entire set of tests . This fails because the static variable is 
already initialized. I guess the classes are pre-initialized by the time the 
testcase is reached 

> JettySolrRunner should not use system properties to pass configuration
> ----------------------------------------------------------------------
>
>                 Key: SOLR-7179
>                 URL: https://issues.apache.org/jira/browse/SOLR-7179
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Alan Woodward
>            Assignee: Alan Woodward
>            Priority: Minor
>         Attachments: SOLR-7179.patch, SOLR-7179.patch, SOLR-7179.patch
>
>
> JettySolrRunner sets a bunch of system properties to pass configuration down 
> to its SolrDispatchFilter and CoreContainer.  This means that we can't launch 
> multiple runners at the same time - sys props must be set up, the runner 
> launched, we wait for solr to start up, then sys props must be changed before 
> the next runner can be instantiated.
> Instead we should be able to pass the relevant properties down to 
> SolrDispatchFilter via the servlet context.  This will allow 
> MiniSolrCloudCluster and the various ZK test cases to start and stop their 
> jetties in parallel, which will speed up individual tests (and with luck 
> speed up the test suite overall as well).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to