lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yasufumi Mizoguchi <yasufumi0...@gmail.com>
Subject Re: Solr 6.6.3 won't start - unrecognized vm option "UseParNewGC" - Java 10.0.1
Date Mon, 14 May 2018 02:45:26 GMT
Instead of setting JAVA_HOME variables, if you want to use Java8 only with
Solr, you can
use SOLR_JAVA_HOME variable in Solr's bin/solr.in.sh script( or
bin\solr.in.cmd if you use Windows.)

e.g. )
SOLR_JAVA_HOME="/home/ubuntu/jdk1.8.0_171"

Regards,
Yasufumi

2018年5月13日(日) 11:17 Alexandre Rafalovitch <arafalov@gmail.com>:

> You may need to set JAVA_HOME or PATH variables to point to your java 8 .
> Possibly both.
>
> Regards,
>      Alex
>
> On Sat, May 12, 2018, 6:28 PM turpentyne, <turpentyne@gmail.com> wrote:
>
> > Erick,
> >
> > Thank you, and sorry for 'beginner' questions!
> >
> > So, I've installed a second version of Java. I believe 8? (Titled:
> > oracle65-1.8.0.172), and I turned it on for the local Solr-6.6.3 folder.
> > Double checked it's using that version (using homebrew, cask and jenv)
> >
> > But... I'm getting exactly the same error still. no such file, and the
> > console.log
> >
> > Java HotSpot(TM) 64-Bit Server VM warning: Option UseConcMarkSweepGC was
> > deprecated in version 9.0 and will likely be removed in a future release.
> > Unrecognized VM option 'UseParNewGC'
> > Error: Could not create the Java Virtual Machine.
> > Error: A fatal exception has occurred. Program will exit.
> >
> > thoughts?
> >
> > On Sat, May 12, 2018 at 2:38 PM, Erick Erickson <erickerickson@gmail.com
> >
> > wrote:
> >
> > > Just what it says, you are using (or rather the start scripts that
> > > Solr 6.6.3 uses) are using options not supported in Java 10.
> > >
> > > Java 10 is in process of being verified to work with Solr, see this
> > > JIRA in the 7.3.1 release notes: SOLR-12141: Fix "bin/solr" shell
> > > scripts (Windows/Linux/Mac) to correctly detect major Java version
> > > and use numerical version comparison to enforce minimum requirements.
> > > Also remove obsolete "UseParNewGC" option.  This allows to start Solr
> > > with Java 10 or later. (Uwe Schindler)
> > >
> > > I'd pretty strongly recommend moving back to the version of Java
> > > specified with 6.6.3, probably Java 9. Java 8 has the most mileage
> > > with that Solr code base.
> > >
> > > Best,
> > > Erick
> > >
> > > On Sat, May 12, 2018 at 5:02 PM, turpentyne <turpentyne@gmail.com>
> > wrote:
> > > > Running into an issue beyond my experience level.
> > > >
> > > >
> > > > In Installed and started Solr 7.3. But, then I realized I need to use
> > an
> > > > older 6.x version (for Drupal)
> > > >
> > > > So, I installed Solr 6.6.3. But, it will not start.
> > > >
> > > > The message I get is:
> > > >
> > > > **Still not seeing Solr listening on 8983 after 180 seconds!*
> > > >
> > > > *tail: /Applications/solr-6.6.3/server/logs/solr.log: No such file or
> > > > directory**
> > > >
> > > > I get the same same result, whether I use *bin/solr start* or *sudo*.
> > > >
> > > > The solr.log is definitely missing. But there is a
> > Solr-8983-console.log.
> > > > This shows the message below:
> > > >
> > > > **Java HotSpot(TM) 64-Bit Server VM warning: Option
> UseConcMarkSweepGC
> > > was
> > > > deprecated in version 9.0 and will likely be removed in a future
> > > release.*
> > > >
> > > > *Unrecognized VM option 'UseParNewGC'*
> > > >
> > > > *Error: Could not create the Java Virtual Machine.*
> > > >
> > > > *Error: A fatal exception has occurred. Program will exit.**
> > > >
> > > > Java -version displays as 10.0.1. This is a work computer with
> security
> > > > needs, and I believe I need to keep it as updated as possible:
> > > >
> > > > **java version "10.0.1" 2018-04-17*
> > > >
> > > > *Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)*
> > > >
> > > > *Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed
> mode)**
> > > >
> > > > Also tried with Solr 6.6.3, 6.6.0 and 5.0.0 with same failure and log
> > > > message.
> > > >
> > > > If relevant, I'm on a 2015 macbook pro, using high sierra 10.13.3
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message