These get added to the startup of Tomcat:
 -DhostPort=8181 -Djetty.port=8181
-DzkHost=localhost:2181,localhost:2182,localhost:2183,localhost:2184,localhost:2185
-Dbootstrap_conf=true -Dport=8181 -DhostContext=solr
-DzkClientTimeout=20000


-- Chris


On Thu, Apr 24, 2014 at 11:41 AM, Rafał Kuć <r....@solr.pl> wrote:

> Hello!
>
> What are the start-up parameters for Tomcat?
>
> --
> Regards,
>  Rafał Kuć
> Performance Monitoring * Log Analytics * Search Analytics
> Solr & Elasticsearch Support * http://sematext.com/
>
>
> > Running Solr 4.6.1, Tomcat 7.0.29, Zookeeper 3.4.6, Java 6
>
> > I have 3 Tomcats running, each with their own Solr war, all on the same
> > box, along with 5 ZK nodes.  It's a dev box.
>
> > I can get the SolrCloud up and running, then use the Collections API to
> get
> > everything going.  It's all fine until I stop Tomcat and restart it.
>  Then
> > I get this error:
>
> > ERROR - 2014-04-24 14:48:08.677;
> > org.apache.solr.servlet.SolrDispatchFilter; Could not start Solr. Check
> > solr/home property and the logs
> > ERROR - 2014-04-24 14:48:08.705; org.apache.solr.common.SolrException;
> > null:java.lang.IllegalArgumentException: Illegal directory:
> > /data/solr1/test_shard1_replica3/conf
> >         at
> > org.apache.solr.cloud.ZkController.uploadToZK(ZkController.java:1331)
> >         at
> >
> org.apache.solr.cloud.ZkController.uploadConfigDir(ZkController.java:1373)
> >         at
> > org.apache.solr.cloud.ZkController.bootstrapConf(ZkController.java:1558)
> >         at
> > org.apache.solr.core.ZkContainer.initZooKeeper(ZkContainer.java:193)
> >         at
> > org.apache.solr.core.ZkContainer.initZooKeeper(ZkContainer.java:73)
> >         at
> > org.apache.solr.core.CoreContainer.load(CoreContainer.java:208)
> >         at
> >
> org.apache.solr.servlet.SolrDispatchFilter.createCoreContainer(SolrDispatchFilter.java:183)
> >         at
> >
> org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:133)
> >         at
> >
> org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:269)
> >         at
> >
> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:258)
> >         at
> >
> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:382)
> >         at
> >
> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:103)
> >         at
> >
> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4650)
> >         at
> >
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5306)
> >         at
> > org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> >         at
> >
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> >         at
> > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> >         at
> > org.apache.catalina.core.StandardHost.addChild(StandardHost.java:618)
> >         at
> >
> org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:650)
> >         at
> >
> org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1582)
> >         at
> > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> >         at
> > java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> >         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> >         at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> >         at
> >
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> >         at java.lang.Thread.run(Thread.java:662)
>
> > From looking at the source, it's trying to upload the conf directories.
> > When I use the API to pull the configs from ZK, it doesn't download a
> conf
> > directory, and I think that's why the error is caused.
>
> > Is there any way around this?  I'm using this dev box to get ready to
> move
> > my production Solr instances up to the newer versions, but I'm worried
> that
> > I'd run into this issue there.
>
> > Any advice would be helpful, let me know if there's anything else I can
> > provide to help debug this.
>
> > Thanks!
>
>
> > -- Chris
>
>

Reply via email to