You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Peter Schmidt <pe...@gmail.com> on 2013/10/10 11:01:32 UTC
Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Hey folks,
for some days i tried to get Solr 4.4.0 working as a webapp with Jetty 6.1
from the Ubuntu repository installed with apt-get. First i tried the
installation according the wiki http://wiki.apache.org/solr/SolrJetty. Then
i found this example
http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/ and
tried the Configuration according to the book pache Solr 4 Cookbook by
Rafal Kuc.
But it semmed to be impossible to run Solr 4.4.0 as webapp on Ubuntus
jetty 6.1 :(
Can somebody confirm that it's impossible or give me an advice how to run
Solr 4.4.0 on Jetty 6.1?
Regards
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Tobias Kabbeck <to...@zeit.de>.
Am 10.10.13 11:05, schrieb Stefan Matheis:
> Is there a specific reason you are trying to use that jetty instead of the provided one?
No not really. I'm already using the provided one.
But since i spend some tries on it i want to know if somebody is
successfully using it that way :)
>
> -Stefan
>
>
> On Thursday, October 10, 2013 at 11:01 AM, Peter Schmidt wrote:
>
>> Hey folks,
>> for some days i tried to get Solr 4.4.0 working as a webapp with Jetty 6.1
>> from the Ubuntu repository installed with apt-get. First i tried the
>> installation according the wiki http://wiki.apache.org/solr/SolrJetty. Then
>> i found this example
>> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/ and
>> tried the Configuration according to the book pache Solr 4 Cookbook by
>> Rafal Kuc.
>> But it semmed to be impossible to run Solr 4.4.0 as webapp on Ubuntus
>> jetty 6.1 :(
>> Can somebody confirm that it's impossible or give me an advice how to run
>> Solr 4.4.0 on Jetty 6.1?
>> Regards
>>
>>
>
--
Tobias Kabbeck
--------------------------
ZEIT ONLINE
Askanischer Platz 1
10963 Berlin
--------------------------
tobias.kabbeck@zeit.de
Tel: +49 (0)30 322 950 175
Mobil: +49 (0)160 96966428
--------------------------
www.zeit.de
DIE ZEIT jetzt am Kiosk.
www.zeit.de/diesewoche
----------------------------------------------------------------
ZEIT ONLINE - Durchschauen Sie jeden Tag.
www.zeit.de
___________________________________________
Zeitverlag Gerd Bucerius GmbH & Co. KG, 20079 Hamburg
Geschäftsführer: Dr. Rainer Esser
Handelsregister Hamburg HRA 91123
Amtsgericht Hamburg
http://www.zeit.de/
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package
Repository
Posted by Stefan Matheis <ma...@gmail.com>.
Is there a specific reason you are trying to use that jetty instead of the provided one?
-Stefan
On Thursday, October 10, 2013 at 11:01 AM, Peter Schmidt wrote:
> Hey folks,
> for some days i tried to get Solr 4.4.0 working as a webapp with Jetty 6.1
> from the Ubuntu repository installed with apt-get. First i tried the
> installation according the wiki http://wiki.apache.org/solr/SolrJetty. Then
> i found this example
> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/ and
> tried the Configuration according to the book pache Solr 4 Cookbook by
> Rafal Kuc.
> But it semmed to be impossible to run Solr 4.4.0 as webapp on Ubuntus
> jetty 6.1 :(
> Can somebody confirm that it's impossible or give me an advice how to run
> Solr 4.4.0 on Jetty 6.1?
> Regards
>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Furkan KAMACI <fu...@gmail.com>.
Hi Peter;
You can learn its version as like that:
java -jar start.jar --version
2013/10/10 Peter Schmidt <pe...@gmail.com>
> Is the integrated jetty in Solr 4.4.0 a jetty version 9 or 7 or 8 ?
>
>
> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>
> > Your right. it worked although for me with Jetty 9. You mean 9.0.6
> > and i was talking about jetty 6.1 which come with ubuntus packing.
> >
> > So i think i would use the solr with the integrated jetty.
> >
> >
> > 2013/10/10 maephisto <my...@yahoo.com>
> >
> >> Tried it and worked as expected with latest version of Jetty (.0.6 if I
> >> remember correctly) and Solr 4.4.0
> >> This tutorial should help you (it's verified by me and working):
> >>
> http://dcvan24.wordpress.com/2013/05/16/how-to-deploy-solr-4-3-on-jetty-9/
> >>
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://lucene.472066.n3.nabble.com/Solr-4-4-0-on-Ubuntu-10-04-with-Jetty-6-1-from-package-Repository-tp4094617p4094646.html
> >> Sent from the Solr - User mailing list archive at Nabble.com.
> >>
> >
> >
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
Is the integrated jetty in Solr 4.4.0 a jetty version 9 or 7 or 8 ?
2013/10/10 Peter Schmidt <pe...@gmail.com>
> Your right. it worked although for me with Jetty 9. You mean 9.0.6
> and i was talking about jetty 6.1 which come with ubuntus packing.
>
> So i think i would use the solr with the integrated jetty.
>
>
> 2013/10/10 maephisto <my...@yahoo.com>
>
>> Tried it and worked as expected with latest version of Jetty (.0.6 if I
>> remember correctly) and Solr 4.4.0
>> This tutorial should help you (it's verified by me and working):
>> http://dcvan24.wordpress.com/2013/05/16/how-to-deploy-solr-4-3-on-jetty-9/
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://lucene.472066.n3.nabble.com/Solr-4-4-0-on-Ubuntu-10-04-with-Jetty-6-1-from-package-Repository-tp4094617p4094646.html
>> Sent from the Solr - User mailing list archive at Nabble.com.
>>
>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
Your right. it worked although for me with Jetty 9. You mean 9.0.6
and i was talking about jetty 6.1 which come with ubuntus packing.
So i think i would use the solr with the integrated jetty.
2013/10/10 maephisto <my...@yahoo.com>
> Tried it and worked as expected with latest version of Jetty (.0.6 if I
> remember correctly) and Solr 4.4.0
> This tutorial should help you (it's verified by me and working):
> http://dcvan24.wordpress.com/2013/05/16/how-to-deploy-solr-4-3-on-jetty-9/
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-4-4-0-on-Ubuntu-10-04-with-Jetty-6-1-from-package-Repository-tp4094617p4094646.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package
Repository
Posted by maephisto <my...@yahoo.com>.
Tried it and worked as expected with latest version of Jetty (.0.6 if I
remember correctly) and Solr 4.4.0
This tutorial should help you (it's verified by me and working):
http://dcvan24.wordpress.com/2013/05/16/how-to-deploy-solr-4-3-on-jetty-9/
--
View this message in context: http://lucene.472066.n3.nabble.com/Solr-4-4-0-on-Ubuntu-10-04-with-Jetty-6-1-from-package-Repository-tp4094617p4094646.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
I can't tell for sure if that is documented somewhere, I did that
straight forward cause of years I have been developing Java webapps, a
class not found usually means that some jar/class is missing somewhere,
because of all the issues I have seen with parent-child class loaders,
my 1st choice is usually to make the jars/classes available to the
relevant webapp classloader, in this case to WEB-INF/lib Solr webapp;
which if running several webapps will require more PERM GEN space, but
in this case is not a problem cause there is only one webapp running
which won't lead to several child class loader loading the same set of
classes from a jar.
I have seen too man weird things with class loaders, well, enough about
class loading, don't want to hijack the subject of this thread,
HTH,
Guido.
On 11/10/13 11:55, Peter Schmidt wrote:
> So the main problem was that the libs must be copied to the WEB-INF/lib
> directory insteed of the jetty lib/ext directory. Is the fact that you
> should you use WEB-INF/lib somewhere documented?
>
>
> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>
>> Not so hard switching it to Oracle JDK 7u40.
>> Just download it and change the JAVA_HOME path in /etc/default/jetty, so
>> it's not nescessary to switch java version with update-java-alternatives
>>
>> The machine is 64bit :)
>>
>>
>>
>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>
>>> Does this work ?
>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>
>>> ???
>>>
>>> Which version of 7 is recommended ?
>>>
>>> Bill Bell
>>> Sent from mobile
>>>
>>>
>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <ds...@mitre.org>
>>> wrote:
>>>> *Don't* use JDK 7u40, it's been known to cause index corruption and
>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been unnoticed by
>>>> Oracle.
>>>>
>>>> ~ David
>>>>
>>>>> On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com> wrote:
>>>>>
>>>>> 2. Java version: There are huges performance winning between Java 5, 6
>>>>> and 7; we use Oracle JDK 7u40.
>>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
But it's used, it's in the JAVA_OPTIONS listet by service jetty check
2013/10/14 Peter Schmidt <pe...@gmail.com>
> But the flag is not listed under the Dashboard->Args in Solr Admin
> Interface.
>
>
> 2013/10/14 Peter Schmidt <pe...@gmail.com>
>
>> It is necessary to configure the update-alternatives for Oracle Java JDK
>> 7. Afterwards i can use the -server flag
>>
>>
>> 2013/10/14 Peter Schmidt <pe...@gmail.com>
>>
>>> I downloaded the Linux 64bit version jdk-7u40-linux-x64.tar.gz
>>>
>>>
>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>
>>>> Then I think you downloaded the wrong JDK 7 (32bits JDK?), if you are
>>>> running JDK 7 64bits the -server flag should be recognized. According to
>>>> the stackoverflow link you mentioned before.
>>>>
>>>> Guido.
>>>>
>>>>
>>>> On 11/10/13 15:48, Peter Schmidt wrote:
>>>>
>>>>> no it is 64bit and just a development VM. In production the solr will
>>>>> use
>>>>> multicore, also 64bit and some gb ram.
>>>>>
>>>>>
>>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>>
>>>>> If your single core is at 32bits use Oracle JDK 7u25 or Ubuntu Open
>>>>>> JDK 7,
>>>>>> the JDK 7u40 for 32bits will corrupt indexes as stated on the lucene
>>>>>> bug
>>>>>> report.
>>>>>>
>>>>>> Guido.
>>>>>>
>>>>>>
>>>>>> On 11/10/13 15:13, Peter Schmidt wrote:
>>>>>>
>>>>>> Oh, i got it http://stackoverflow.com/a/****5273166/326905<http://stackoverflow.com/a/**5273166/326905>
>>>>>>> <http://**stackoverflow.com/a/5273166/**326905<http://stackoverflow.com/a/5273166/326905>
>>>>>>> >
>>>>>>>
>>>>>>>
>>>>>>> "at least 2 cores and at least 2 GB physical memory"
>>>>>>>
>>>>>>> Until know i'm using a VM with single core and 1GB RAM.
>>>>>>>
>>>>>>> So this will be later for production :)
>>>>>>>
>>>>>>> Thank you Guido.
>>>>>>>
>>>>>>>
>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>
>>>>>>> Strange. When i add "-server" to the arguments, i got everytime
>>>>>>> the error
>>>>>>>
>>>>>>>> on jetty startup
>>>>>>>>
>>>>>>>>
>>>>>>>> Invalid option -server
>>>>>>>> Cannot parse command line arguments
>>>>>>>>
>>>>>>>>
>>>>>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>>>>>
>>>>>>>> It is JVM parameter, example:
>>>>>>>>
>>>>>>>>> JAVA_OPTIONS="-Djava.awt.******headless=true -Dfile.encoding=UTF-8
>>>>>>>>>
>>>>>>>>> -server
>>>>>>>>>
>>>>>>>>> -Xms256m -Xmx256m"
>>>>>>>>>
>>>>>>>>> If you want to concatenate more JVM parameters you do it like this:
>>>>>>>>> JAVA_OPTIONS="-Dsolr.solr.******home=/usr/share/solr
>>>>>>>>> $JAVA_OPTIONS"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Take a good look at the format,
>>>>>>>>>
>>>>>>>>> Guido.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 11/10/13 13:37, Peter Schmidt wrote:
>>>>>>>>>
>>>>>>>>> @Guido: Itried it before and than i thought you marked just the
>>>>>>>>> server
>>>>>>>>>
>>>>>>>>>> options
>>>>>>>>>>
>>>>>>>>>> Because the -sever causes a:
>>>>>>>>>>
>>>>>>>>>> sudo service jetty start
>>>>>>>>>> * Starting Jetty servlet engine.
>>>>>>>>>> jetty
>>>>>>>>>> Invalid option -server
>>>>>>>>>> Cannot parse command line arguments
>>>>>>>>>>
>>>>>>>>>> Or should i substitute server with ...?
>>>>>>>>>>
>>>>>>>>>> Options with -server:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> JAVA_OPTIONS="-Djava.awt.******headless=true
>>>>>>>>>> -Dfile.encoding=UTF-8
>>>>>>>>>>
>>>>>>>>>> -server
>>>>>>>>>>
>>>>>>>>>> -Xms256m -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache
>>>>>>>>>> -Dsolr.solr.home=/usr/share/******solr $JAVA_OPTIONS"
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>>>>>>>
>>>>>>>>>> Remember the "-server" which for Java webapps or dedicated Java
>>>>>>>>>> services
>>>>>>>>>>
>>>>>>>>>> will improve things.
>>>>>>>>>>>
>>>>>>>>>>> Guido.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 11/10/13 12:26, Peter Schmidt wrote:
>>>>>>>>>>>
>>>>>>>>>>> I can report that jetty is running now with this options:
>>>>>>>>>>>
>>>>>>>>>>> JAVA_OPTIONS="-Djava.awt.********headless=true
>>>>>>>>>>>> -Dfile.encoding=UTF-8
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> -Xms256m
>>>>>>>>>>>>
>>>>>>>>>>>> -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>>>>>>> -XX:+OptimizeStringConcat
>>>>>>>>>>>> -XX:+UseStringCache -Dsolr.solr.home=/usr/share/********solr
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> $JAVA_OPTIONS"
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> @Guido: I reduced the min/max heap size to 256m, i will
>>>>>>>>>>>> increase this
>>>>>>>>>>>> on
>>>>>>>>>>>> production server.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>>>>
>>>>>>>>>>>> So the main problem was that the libs must be copied to the
>>>>>>>>>>>> WEB-INF/lib
>>>>>>>>>>>>
>>>>>>>>>>>> directory insteed of the jetty lib/ext directory. Is the fact
>>>>>>>>>>>> that
>>>>>>>>>>>>
>>>>>>>>>>>>> you
>>>>>>>>>>>>> should you use WEB-INF/lib somewhere documented?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Not so hard switching it to Oracle JDK 7u40.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Just download it and change the JAVA_HOME path in
>>>>>>>>>>>>>
>>>>>>>>>>>>>> /etc/default/jetty, so
>>>>>>>>>>>>>> it's not nescessary to switch java version with
>>>>>>>>>>>>>> update-java-alternatives
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The machine is 64bit :)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Does this work ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I can suggest -XX:-UseLoopPredicate to switch off
>>>>>>>>>>>>>> predicates.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ???
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Which version of 7 is recommended ?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Bill Bell
>>>>>>>>>>>>>>> Sent from mobile
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <
>>>>>>>>>>>>>>> dsmiley@mitre.org>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> *Don't* use JDK 7u40, it's been known to cause index
>>>>>>>>>>>>>>> corruption
>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been
>>>>>>>>>>>>>>>> unnoticed
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> by
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Oracle.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ~ David
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On 10/10/13 12:34 PM, "Guido Medina" <
>>>>>>>>>>>>>>>> guido.medina@temetra.com>
>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> 2. Java version: There are huges performance winning
>>>>>>>>>>>>>>>> between Java
>>>>>>>>>>>>>>>> 5, 6
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> and 7; we use Oracle JDK 7u40.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>
>>>
>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
But the flag is not listed under the Dashboard->Args in Solr Admin
Interface.
2013/10/14 Peter Schmidt <pe...@gmail.com>
> It is necessary to configure the update-alternatives for Oracle Java JDK
> 7. Afterwards i can use the -server flag
>
>
> 2013/10/14 Peter Schmidt <pe...@gmail.com>
>
>> I downloaded the Linux 64bit version jdk-7u40-linux-x64.tar.gz
>>
>>
>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>
>>> Then I think you downloaded the wrong JDK 7 (32bits JDK?), if you are
>>> running JDK 7 64bits the -server flag should be recognized. According to
>>> the stackoverflow link you mentioned before.
>>>
>>> Guido.
>>>
>>>
>>> On 11/10/13 15:48, Peter Schmidt wrote:
>>>
>>>> no it is 64bit and just a development VM. In production the solr will
>>>> use
>>>> multicore, also 64bit and some gb ram.
>>>>
>>>>
>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>
>>>> If your single core is at 32bits use Oracle JDK 7u25 or Ubuntu Open
>>>>> JDK 7,
>>>>> the JDK 7u40 for 32bits will corrupt indexes as stated on the lucene
>>>>> bug
>>>>> report.
>>>>>
>>>>> Guido.
>>>>>
>>>>>
>>>>> On 11/10/13 15:13, Peter Schmidt wrote:
>>>>>
>>>>> Oh, i got it http://stackoverflow.com/a/****5273166/326905<http://stackoverflow.com/a/**5273166/326905>
>>>>>> <http://**stackoverflow.com/a/5273166/**326905<http://stackoverflow.com/a/5273166/326905>
>>>>>> >
>>>>>>
>>>>>>
>>>>>> "at least 2 cores and at least 2 GB physical memory"
>>>>>>
>>>>>> Until know i'm using a VM with single core and 1GB RAM.
>>>>>>
>>>>>> So this will be later for production :)
>>>>>>
>>>>>> Thank you Guido.
>>>>>>
>>>>>>
>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>
>>>>>> Strange. When i add "-server" to the arguments, i got everytime the
>>>>>> error
>>>>>>
>>>>>>> on jetty startup
>>>>>>>
>>>>>>>
>>>>>>> Invalid option -server
>>>>>>> Cannot parse command line arguments
>>>>>>>
>>>>>>>
>>>>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>>>>
>>>>>>> It is JVM parameter, example:
>>>>>>>
>>>>>>>> JAVA_OPTIONS="-Djava.awt.******headless=true -Dfile.encoding=UTF-8
>>>>>>>>
>>>>>>>> -server
>>>>>>>>
>>>>>>>> -Xms256m -Xmx256m"
>>>>>>>>
>>>>>>>> If you want to concatenate more JVM parameters you do it like this:
>>>>>>>> JAVA_OPTIONS="-Dsolr.solr.******home=/usr/share/solr $JAVA_OPTIONS"
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Take a good look at the format,
>>>>>>>>
>>>>>>>> Guido.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 11/10/13 13:37, Peter Schmidt wrote:
>>>>>>>>
>>>>>>>> @Guido: Itried it before and than i thought you marked just the
>>>>>>>> server
>>>>>>>>
>>>>>>>>> options
>>>>>>>>>
>>>>>>>>> Because the -sever causes a:
>>>>>>>>>
>>>>>>>>> sudo service jetty start
>>>>>>>>> * Starting Jetty servlet engine.
>>>>>>>>> jetty
>>>>>>>>> Invalid option -server
>>>>>>>>> Cannot parse command line arguments
>>>>>>>>>
>>>>>>>>> Or should i substitute server with ...?
>>>>>>>>>
>>>>>>>>> Options with -server:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> JAVA_OPTIONS="-Djava.awt.******headless=true -Dfile.encoding=UTF-8
>>>>>>>>>
>>>>>>>>> -server
>>>>>>>>>
>>>>>>>>> -Xms256m -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache
>>>>>>>>> -Dsolr.solr.home=/usr/share/******solr $JAVA_OPTIONS"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>>>>>>
>>>>>>>>> Remember the "-server" which for Java webapps or dedicated Java
>>>>>>>>> services
>>>>>>>>>
>>>>>>>>> will improve things.
>>>>>>>>>>
>>>>>>>>>> Guido.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 11/10/13 12:26, Peter Schmidt wrote:
>>>>>>>>>>
>>>>>>>>>> I can report that jetty is running now with this options:
>>>>>>>>>>
>>>>>>>>>> JAVA_OPTIONS="-Djava.awt.********headless=true
>>>>>>>>>>> -Dfile.encoding=UTF-8
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> -Xms256m
>>>>>>>>>>>
>>>>>>>>>>> -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>>>>>> -XX:+OptimizeStringConcat
>>>>>>>>>>> -XX:+UseStringCache -Dsolr.solr.home=/usr/share/********solr
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> $JAVA_OPTIONS"
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> @Guido: I reduced the min/max heap size to 256m, i will increase
>>>>>>>>>>> this
>>>>>>>>>>> on
>>>>>>>>>>> production server.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>>>
>>>>>>>>>>> So the main problem was that the libs must be copied to the
>>>>>>>>>>> WEB-INF/lib
>>>>>>>>>>>
>>>>>>>>>>> directory insteed of the jetty lib/ext directory. Is the fact
>>>>>>>>>>> that
>>>>>>>>>>>
>>>>>>>>>>>> you
>>>>>>>>>>>> should you use WEB-INF/lib somewhere documented?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>>>>
>>>>>>>>>>>> Not so hard switching it to Oracle JDK 7u40.
>>>>>>>>>>>>
>>>>>>>>>>>> Just download it and change the JAVA_HOME path in
>>>>>>>>>>>>
>>>>>>>>>>>>> /etc/default/jetty, so
>>>>>>>>>>>>> it's not nescessary to switch java version with
>>>>>>>>>>>>> update-java-alternatives
>>>>>>>>>>>>>
>>>>>>>>>>>>> The machine is 64bit :)
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Does this work ?
>>>>>>>>>>>>>
>>>>>>>>>>>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>>>>>>>>>>>
>>>>>>>>>>>>>> ???
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Which version of 7 is recommended ?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Bill Bell
>>>>>>>>>>>>>> Sent from mobile
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <
>>>>>>>>>>>>>> dsmiley@mitre.org>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> *Don't* use JDK 7u40, it's been known to cause index
>>>>>>>>>>>>>> corruption
>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been
>>>>>>>>>>>>>>> unnoticed
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> by
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Oracle.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ~ David
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 10/10/13 12:34 PM, "Guido Medina" <
>>>>>>>>>>>>>>> guido.medina@temetra.com>
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>> 2. Java version: There are huges performance winning between
>>>>>>>>>>>>>>> Java
>>>>>>>>>>>>>>> 5, 6
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> and 7; we use Oracle JDK 7u40.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>
>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
It is necessary to configure the update-alternatives for Oracle Java JDK 7.
Afterwards i can use the -server flag
2013/10/14 Peter Schmidt <pe...@gmail.com>
> I downloaded the Linux 64bit version jdk-7u40-linux-x64.tar.gz
>
>
> 2013/10/11 Guido Medina <gu...@temetra.com>
>
>> Then I think you downloaded the wrong JDK 7 (32bits JDK?), if you are
>> running JDK 7 64bits the -server flag should be recognized. According to
>> the stackoverflow link you mentioned before.
>>
>> Guido.
>>
>>
>> On 11/10/13 15:48, Peter Schmidt wrote:
>>
>>> no it is 64bit and just a development VM. In production the solr will use
>>> multicore, also 64bit and some gb ram.
>>>
>>>
>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>
>>> If your single core is at 32bits use Oracle JDK 7u25 or Ubuntu Open JDK
>>>> 7,
>>>> the JDK 7u40 for 32bits will corrupt indexes as stated on the lucene bug
>>>> report.
>>>>
>>>> Guido.
>>>>
>>>>
>>>> On 11/10/13 15:13, Peter Schmidt wrote:
>>>>
>>>> Oh, i got it http://stackoverflow.com/a/****5273166/326905<http://stackoverflow.com/a/**5273166/326905>
>>>>> <http://**stackoverflow.com/a/5273166/**326905<http://stackoverflow.com/a/5273166/326905>
>>>>> >
>>>>>
>>>>>
>>>>> "at least 2 cores and at least 2 GB physical memory"
>>>>>
>>>>> Until know i'm using a VM with single core and 1GB RAM.
>>>>>
>>>>> So this will be later for production :)
>>>>>
>>>>> Thank you Guido.
>>>>>
>>>>>
>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>
>>>>> Strange. When i add "-server" to the arguments, i got everytime the
>>>>> error
>>>>>
>>>>>> on jetty startup
>>>>>>
>>>>>>
>>>>>> Invalid option -server
>>>>>> Cannot parse command line arguments
>>>>>>
>>>>>>
>>>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>>>
>>>>>> It is JVM parameter, example:
>>>>>>
>>>>>>> JAVA_OPTIONS="-Djava.awt.******headless=true -Dfile.encoding=UTF-8
>>>>>>>
>>>>>>> -server
>>>>>>>
>>>>>>> -Xms256m -Xmx256m"
>>>>>>>
>>>>>>> If you want to concatenate more JVM parameters you do it like this:
>>>>>>> JAVA_OPTIONS="-Dsolr.solr.******home=/usr/share/solr $JAVA_OPTIONS"
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Take a good look at the format,
>>>>>>>
>>>>>>> Guido.
>>>>>>>
>>>>>>>
>>>>>>> On 11/10/13 13:37, Peter Schmidt wrote:
>>>>>>>
>>>>>>> @Guido: Itried it before and than i thought you marked just the
>>>>>>> server
>>>>>>>
>>>>>>>> options
>>>>>>>>
>>>>>>>> Because the -sever causes a:
>>>>>>>>
>>>>>>>> sudo service jetty start
>>>>>>>> * Starting Jetty servlet engine.
>>>>>>>> jetty
>>>>>>>> Invalid option -server
>>>>>>>> Cannot parse command line arguments
>>>>>>>>
>>>>>>>> Or should i substitute server with ...?
>>>>>>>>
>>>>>>>> Options with -server:
>>>>>>>>
>>>>>>>>
>>>>>>>> JAVA_OPTIONS="-Djava.awt.******headless=true -Dfile.encoding=UTF-8
>>>>>>>>
>>>>>>>> -server
>>>>>>>>
>>>>>>>> -Xms256m -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache
>>>>>>>> -Dsolr.solr.home=/usr/share/******solr $JAVA_OPTIONS"
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>>>>>
>>>>>>>> Remember the "-server" which for Java webapps or dedicated Java
>>>>>>>> services
>>>>>>>>
>>>>>>>> will improve things.
>>>>>>>>>
>>>>>>>>> Guido.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 11/10/13 12:26, Peter Schmidt wrote:
>>>>>>>>>
>>>>>>>>> I can report that jetty is running now with this options:
>>>>>>>>>
>>>>>>>>> JAVA_OPTIONS="-Djava.awt.********headless=true
>>>>>>>>>> -Dfile.encoding=UTF-8
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -Xms256m
>>>>>>>>>>
>>>>>>>>>> -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>>>>> -XX:+OptimizeStringConcat
>>>>>>>>>> -XX:+UseStringCache -Dsolr.solr.home=/usr/share/********solr
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> $JAVA_OPTIONS"
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> @Guido: I reduced the min/max heap size to 256m, i will increase
>>>>>>>>>> this
>>>>>>>>>> on
>>>>>>>>>> production server.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>>
>>>>>>>>>> So the main problem was that the libs must be copied to the
>>>>>>>>>> WEB-INF/lib
>>>>>>>>>>
>>>>>>>>>> directory insteed of the jetty lib/ext directory. Is the fact
>>>>>>>>>> that
>>>>>>>>>>
>>>>>>>>>>> you
>>>>>>>>>>> should you use WEB-INF/lib somewhere documented?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>>>
>>>>>>>>>>> Not so hard switching it to Oracle JDK 7u40.
>>>>>>>>>>>
>>>>>>>>>>> Just download it and change the JAVA_HOME path in
>>>>>>>>>>>
>>>>>>>>>>>> /etc/default/jetty, so
>>>>>>>>>>>> it's not nescessary to switch java version with
>>>>>>>>>>>> update-java-alternatives
>>>>>>>>>>>>
>>>>>>>>>>>> The machine is 64bit :)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>>>>>>>>>>>
>>>>>>>>>>>> Does this work ?
>>>>>>>>>>>>
>>>>>>>>>>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>>>>>>>>>>
>>>>>>>>>>>>> ???
>>>>>>>>>>>>>
>>>>>>>>>>>>> Which version of 7 is recommended ?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Bill Bell
>>>>>>>>>>>>> Sent from mobile
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <
>>>>>>>>>>>>> dsmiley@mitre.org>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> *Don't* use JDK 7u40, it's been known to cause index
>>>>>>>>>>>>> corruption
>>>>>>>>>>>>> and
>>>>>>>>>>>>>
>>>>>>>>>>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been
>>>>>>>>>>>>>> unnoticed
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> by
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Oracle.
>>>>>>>>>>>>>
>>>>>>>>>>>>> ~ David
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On 10/10/13 12:34 PM, "Guido Medina" <
>>>>>>>>>>>>>> guido.medina@temetra.com>
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 2. Java version: There are huges performance winning between
>>>>>>>>>>>>>> Java
>>>>>>>>>>>>>> 5, 6
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> and 7; we use Oracle JDK 7u40.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
I downloaded the Linux 64bit version jdk-7u40-linux-x64.tar.gz
2013/10/11 Guido Medina <gu...@temetra.com>
> Then I think you downloaded the wrong JDK 7 (32bits JDK?), if you are
> running JDK 7 64bits the -server flag should be recognized. According to
> the stackoverflow link you mentioned before.
>
> Guido.
>
>
> On 11/10/13 15:48, Peter Schmidt wrote:
>
>> no it is 64bit and just a development VM. In production the solr will use
>> multicore, also 64bit and some gb ram.
>>
>>
>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>
>> If your single core is at 32bits use Oracle JDK 7u25 or Ubuntu Open JDK
>>> 7,
>>> the JDK 7u40 for 32bits will corrupt indexes as stated on the lucene bug
>>> report.
>>>
>>> Guido.
>>>
>>>
>>> On 11/10/13 15:13, Peter Schmidt wrote:
>>>
>>> Oh, i got it http://stackoverflow.com/a/****5273166/326905<http://stackoverflow.com/a/**5273166/326905>
>>>> <http://**stackoverflow.com/a/5273166/**326905<http://stackoverflow.com/a/5273166/326905>
>>>> >
>>>>
>>>>
>>>> "at least 2 cores and at least 2 GB physical memory"
>>>>
>>>> Until know i'm using a VM with single core and 1GB RAM.
>>>>
>>>> So this will be later for production :)
>>>>
>>>> Thank you Guido.
>>>>
>>>>
>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>
>>>> Strange. When i add "-server" to the arguments, i got everytime the
>>>> error
>>>>
>>>>> on jetty startup
>>>>>
>>>>>
>>>>> Invalid option -server
>>>>> Cannot parse command line arguments
>>>>>
>>>>>
>>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>>
>>>>> It is JVM parameter, example:
>>>>>
>>>>>> JAVA_OPTIONS="-Djava.awt.******headless=true -Dfile.encoding=UTF-8
>>>>>>
>>>>>> -server
>>>>>>
>>>>>> -Xms256m -Xmx256m"
>>>>>>
>>>>>> If you want to concatenate more JVM parameters you do it like this:
>>>>>> JAVA_OPTIONS="-Dsolr.solr.******home=/usr/share/solr $JAVA_OPTIONS"
>>>>>>
>>>>>>
>>>>>>
>>>>>> Take a good look at the format,
>>>>>>
>>>>>> Guido.
>>>>>>
>>>>>>
>>>>>> On 11/10/13 13:37, Peter Schmidt wrote:
>>>>>>
>>>>>> @Guido: Itried it before and than i thought you marked just the
>>>>>> server
>>>>>>
>>>>>>> options
>>>>>>>
>>>>>>> Because the -sever causes a:
>>>>>>>
>>>>>>> sudo service jetty start
>>>>>>> * Starting Jetty servlet engine.
>>>>>>> jetty
>>>>>>> Invalid option -server
>>>>>>> Cannot parse command line arguments
>>>>>>>
>>>>>>> Or should i substitute server with ...?
>>>>>>>
>>>>>>> Options with -server:
>>>>>>>
>>>>>>>
>>>>>>> JAVA_OPTIONS="-Djava.awt.******headless=true -Dfile.encoding=UTF-8
>>>>>>>
>>>>>>> -server
>>>>>>>
>>>>>>> -Xms256m -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache
>>>>>>> -Dsolr.solr.home=/usr/share/******solr $JAVA_OPTIONS"
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>>>>
>>>>>>> Remember the "-server" which for Java webapps or dedicated Java
>>>>>>> services
>>>>>>>
>>>>>>> will improve things.
>>>>>>>>
>>>>>>>> Guido.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 11/10/13 12:26, Peter Schmidt wrote:
>>>>>>>>
>>>>>>>> I can report that jetty is running now with this options:
>>>>>>>>
>>>>>>>> JAVA_OPTIONS="-Djava.awt.********headless=true
>>>>>>>>> -Dfile.encoding=UTF-8
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -Xms256m
>>>>>>>>>
>>>>>>>>> -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>>>> -XX:+OptimizeStringConcat
>>>>>>>>> -XX:+UseStringCache -Dsolr.solr.home=/usr/share/********solr
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> $JAVA_OPTIONS"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> @Guido: I reduced the min/max heap size to 256m, i will increase
>>>>>>>>> this
>>>>>>>>> on
>>>>>>>>> production server.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>
>>>>>>>>> So the main problem was that the libs must be copied to the
>>>>>>>>> WEB-INF/lib
>>>>>>>>>
>>>>>>>>> directory insteed of the jetty lib/ext directory. Is the fact
>>>>>>>>> that
>>>>>>>>>
>>>>>>>>>> you
>>>>>>>>>> should you use WEB-INF/lib somewhere documented?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>>
>>>>>>>>>> Not so hard switching it to Oracle JDK 7u40.
>>>>>>>>>>
>>>>>>>>>> Just download it and change the JAVA_HOME path in
>>>>>>>>>>
>>>>>>>>>>> /etc/default/jetty, so
>>>>>>>>>>> it's not nescessary to switch java version with
>>>>>>>>>>> update-java-alternatives
>>>>>>>>>>>
>>>>>>>>>>> The machine is 64bit :)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>>>>>>>>>>
>>>>>>>>>>> Does this work ?
>>>>>>>>>>>
>>>>>>>>>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>>>>>>>>>
>>>>>>>>>>>> ???
>>>>>>>>>>>>
>>>>>>>>>>>> Which version of 7 is recommended ?
>>>>>>>>>>>>
>>>>>>>>>>>> Bill Bell
>>>>>>>>>>>> Sent from mobile
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <
>>>>>>>>>>>> dsmiley@mitre.org>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> *Don't* use JDK 7u40, it's been known to cause index
>>>>>>>>>>>> corruption
>>>>>>>>>>>> and
>>>>>>>>>>>>
>>>>>>>>>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been
>>>>>>>>>>>>> unnoticed
>>>>>>>>>>>>>
>>>>>>>>>>>>> by
>>>>>>>>>>>>>
>>>>>>>>>>>>> Oracle.
>>>>>>>>>>>>
>>>>>>>>>>>> ~ David
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 10/10/13 12:34 PM, "Guido Medina" <
>>>>>>>>>>>>> guido.medina@temetra.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>> 2. Java version: There are huges performance winning between
>>>>>>>>>>>>> Java
>>>>>>>>>>>>> 5, 6
>>>>>>>>>>>>>
>>>>>>>>>>>>> and 7; we use Oracle JDK 7u40.
>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
Then I think you downloaded the wrong JDK 7 (32bits JDK?), if you are
running JDK 7 64bits the -server flag should be recognized. According to
the stackoverflow link you mentioned before.
Guido.
On 11/10/13 15:48, Peter Schmidt wrote:
> no it is 64bit and just a development VM. In production the solr will use
> multicore, also 64bit and some gb ram.
>
>
> 2013/10/11 Guido Medina <gu...@temetra.com>
>
>> If your single core is at 32bits use Oracle JDK 7u25 or Ubuntu Open JDK 7,
>> the JDK 7u40 for 32bits will corrupt indexes as stated on the lucene bug
>> report.
>>
>> Guido.
>>
>>
>> On 11/10/13 15:13, Peter Schmidt wrote:
>>
>>> Oh, i got it http://stackoverflow.com/a/**5273166/326905<http://stackoverflow.com/a/5273166/326905>
>>>
>>> "at least 2 cores and at least 2 GB physical memory"
>>>
>>> Until know i'm using a VM with single core and 1GB RAM.
>>>
>>> So this will be later for production :)
>>>
>>> Thank you Guido.
>>>
>>>
>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>
>>> Strange. When i add "-server" to the arguments, i got everytime the error
>>>> on jetty startup
>>>>
>>>>
>>>> Invalid option -server
>>>> Cannot parse command line arguments
>>>>
>>>>
>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>
>>>> It is JVM parameter, example:
>>>>> JAVA_OPTIONS="-Djava.awt.****headless=true -Dfile.encoding=UTF-8
>>>>> -server
>>>>>
>>>>> -Xms256m -Xmx256m"
>>>>>
>>>>> If you want to concatenate more JVM parameters you do it like this:
>>>>> JAVA_OPTIONS="-Dsolr.solr.****home=/usr/share/solr $JAVA_OPTIONS"
>>>>>
>>>>>
>>>>> Take a good look at the format,
>>>>>
>>>>> Guido.
>>>>>
>>>>>
>>>>> On 11/10/13 13:37, Peter Schmidt wrote:
>>>>>
>>>>> @Guido: Itried it before and than i thought you marked just the server
>>>>>> options
>>>>>>
>>>>>> Because the -sever causes a:
>>>>>>
>>>>>> sudo service jetty start
>>>>>> * Starting Jetty servlet engine.
>>>>>> jetty
>>>>>> Invalid option -server
>>>>>> Cannot parse command line arguments
>>>>>>
>>>>>> Or should i substitute server with ...?
>>>>>>
>>>>>> Options with -server:
>>>>>>
>>>>>>
>>>>>> JAVA_OPTIONS="-Djava.awt.****headless=true -Dfile.encoding=UTF-8
>>>>>> -server
>>>>>>
>>>>>> -Xms256m -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache
>>>>>> -Dsolr.solr.home=/usr/share/****solr $JAVA_OPTIONS"
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>>>
>>>>>> Remember the "-server" which for Java webapps or dedicated Java
>>>>>> services
>>>>>>
>>>>>>> will improve things.
>>>>>>>
>>>>>>> Guido.
>>>>>>>
>>>>>>>
>>>>>>> On 11/10/13 12:26, Peter Schmidt wrote:
>>>>>>>
>>>>>>> I can report that jetty is running now with this options:
>>>>>>>
>>>>>>>> JAVA_OPTIONS="-Djava.awt.******headless=true -Dfile.encoding=UTF-8
>>>>>>>>
>>>>>>>> -Xms256m
>>>>>>>>
>>>>>>>> -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>>> -XX:+OptimizeStringConcat
>>>>>>>> -XX:+UseStringCache -Dsolr.solr.home=/usr/share/******solr
>>>>>>>>
>>>>>>>> $JAVA_OPTIONS"
>>>>>>>>
>>>>>>>>
>>>>>>>> @Guido: I reduced the min/max heap size to 256m, i will increase this
>>>>>>>> on
>>>>>>>> production server.
>>>>>>>>
>>>>>>>>
>>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>>
>>>>>>>> So the main problem was that the libs must be copied to the
>>>>>>>> WEB-INF/lib
>>>>>>>>
>>>>>>>> directory insteed of the jetty lib/ext directory. Is the fact that
>>>>>>>>> you
>>>>>>>>> should you use WEB-INF/lib somewhere documented?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>
>>>>>>>>> Not so hard switching it to Oracle JDK 7u40.
>>>>>>>>>
>>>>>>>>> Just download it and change the JAVA_HOME path in
>>>>>>>>>> /etc/default/jetty, so
>>>>>>>>>> it's not nescessary to switch java version with
>>>>>>>>>> update-java-alternatives
>>>>>>>>>>
>>>>>>>>>> The machine is 64bit :)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>>>>>>>>>
>>>>>>>>>> Does this work ?
>>>>>>>>>>
>>>>>>>>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>>>>>>>>> ???
>>>>>>>>>>>
>>>>>>>>>>> Which version of 7 is recommended ?
>>>>>>>>>>>
>>>>>>>>>>> Bill Bell
>>>>>>>>>>> Sent from mobile
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <
>>>>>>>>>>> dsmiley@mitre.org>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> *Don't* use JDK 7u40, it's been known to cause index corruption
>>>>>>>>>>> and
>>>>>>>>>>>
>>>>>>>>>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been
>>>>>>>>>>>> unnoticed
>>>>>>>>>>>>
>>>>>>>>>>>> by
>>>>>>>>>>>>
>>>>>>>>>>> Oracle.
>>>>>>>>>>>
>>>>>>>>>>>> ~ David
>>>>>>>>>>>>
>>>>>>>>>>>> On 10/10/13 12:34 PM, "Guido Medina" <
>>>>>>>>>>>> guido.medina@temetra.com>
>>>>>>>>>>>> wrote:
>>>>>>>>>>>> 2. Java version: There are huges performance winning between Java
>>>>>>>>>>>> 5, 6
>>>>>>>>>>>>
>>>>>>>>>>>> and 7; we use Oracle JDK 7u40.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
no it is 64bit and just a development VM. In production the solr will use
multicore, also 64bit and some gb ram.
2013/10/11 Guido Medina <gu...@temetra.com>
> If your single core is at 32bits use Oracle JDK 7u25 or Ubuntu Open JDK 7,
> the JDK 7u40 for 32bits will corrupt indexes as stated on the lucene bug
> report.
>
> Guido.
>
>
> On 11/10/13 15:13, Peter Schmidt wrote:
>
>> Oh, i got it http://stackoverflow.com/a/**5273166/326905<http://stackoverflow.com/a/5273166/326905>
>>
>> "at least 2 cores and at least 2 GB physical memory"
>>
>> Until know i'm using a VM with single core and 1GB RAM.
>>
>> So this will be later for production :)
>>
>> Thank you Guido.
>>
>>
>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>
>> Strange. When i add "-server" to the arguments, i got everytime the error
>>> on jetty startup
>>>
>>>
>>> Invalid option -server
>>> Cannot parse command line arguments
>>>
>>>
>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>
>>> It is JVM parameter, example:
>>>>
>>>> JAVA_OPTIONS="-Djava.awt.****headless=true -Dfile.encoding=UTF-8
>>>> -server
>>>>
>>>> -Xms256m -Xmx256m"
>>>>
>>>> If you want to concatenate more JVM parameters you do it like this:
>>>> JAVA_OPTIONS="-Dsolr.solr.****home=/usr/share/solr $JAVA_OPTIONS"
>>>>
>>>>
>>>> Take a good look at the format,
>>>>
>>>> Guido.
>>>>
>>>>
>>>> On 11/10/13 13:37, Peter Schmidt wrote:
>>>>
>>>> @Guido: Itried it before and than i thought you marked just the server
>>>>> options
>>>>>
>>>>> Because the -sever causes a:
>>>>>
>>>>> sudo service jetty start
>>>>> * Starting Jetty servlet engine.
>>>>> jetty
>>>>> Invalid option -server
>>>>> Cannot parse command line arguments
>>>>>
>>>>> Or should i substitute server with ...?
>>>>>
>>>>> Options with -server:
>>>>>
>>>>>
>>>>> JAVA_OPTIONS="-Djava.awt.****headless=true -Dfile.encoding=UTF-8
>>>>> -server
>>>>>
>>>>> -Xms256m -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache
>>>>> -Dsolr.solr.home=/usr/share/****solr $JAVA_OPTIONS"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>>
>>>>> Remember the "-server" which for Java webapps or dedicated Java
>>>>> services
>>>>>
>>>>>> will improve things.
>>>>>>
>>>>>> Guido.
>>>>>>
>>>>>>
>>>>>> On 11/10/13 12:26, Peter Schmidt wrote:
>>>>>>
>>>>>> I can report that jetty is running now with this options:
>>>>>>
>>>>>>> JAVA_OPTIONS="-Djava.awt.******headless=true -Dfile.encoding=UTF-8
>>>>>>>
>>>>>>> -Xms256m
>>>>>>>
>>>>>>> -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>> -XX:+OptimizeStringConcat
>>>>>>> -XX:+UseStringCache -Dsolr.solr.home=/usr/share/******solr
>>>>>>>
>>>>>>> $JAVA_OPTIONS"
>>>>>>>
>>>>>>>
>>>>>>> @Guido: I reduced the min/max heap size to 256m, i will increase this
>>>>>>> on
>>>>>>> production server.
>>>>>>>
>>>>>>>
>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>
>>>>>>> So the main problem was that the libs must be copied to the
>>>>>>> WEB-INF/lib
>>>>>>>
>>>>>>> directory insteed of the jetty lib/ext directory. Is the fact that
>>>>>>>> you
>>>>>>>> should you use WEB-INF/lib somewhere documented?
>>>>>>>>
>>>>>>>>
>>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>>
>>>>>>>> Not so hard switching it to Oracle JDK 7u40.
>>>>>>>>
>>>>>>>> Just download it and change the JAVA_HOME path in
>>>>>>>>> /etc/default/jetty, so
>>>>>>>>> it's not nescessary to switch java version with
>>>>>>>>> update-java-alternatives
>>>>>>>>>
>>>>>>>>> The machine is 64bit :)
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>>>>>>>>
>>>>>>>>> Does this work ?
>>>>>>>>>
>>>>>>>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>>>>>>>>
>>>>>>>>>> ???
>>>>>>>>>>
>>>>>>>>>> Which version of 7 is recommended ?
>>>>>>>>>>
>>>>>>>>>> Bill Bell
>>>>>>>>>> Sent from mobile
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <
>>>>>>>>>> dsmiley@mitre.org>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> *Don't* use JDK 7u40, it's been known to cause index corruption
>>>>>>>>>> and
>>>>>>>>>>
>>>>>>>>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been
>>>>>>>>>>> unnoticed
>>>>>>>>>>>
>>>>>>>>>>> by
>>>>>>>>>>>
>>>>>>>>>> Oracle.
>>>>>>>>>>
>>>>>>>>>>> ~ David
>>>>>>>>>>>
>>>>>>>>>>> On 10/10/13 12:34 PM, "Guido Medina" <
>>>>>>>>>>> guido.medina@temetra.com>
>>>>>>>>>>> wrote:
>>>>>>>>>>> 2. Java version: There are huges performance winning between Java
>>>>>>>>>>> 5, 6
>>>>>>>>>>>
>>>>>>>>>>> and 7; we use Oracle JDK 7u40.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
If your single core is at 32bits use Oracle JDK 7u25 or Ubuntu Open JDK
7, the JDK 7u40 for 32bits will corrupt indexes as stated on the lucene
bug report.
Guido.
On 11/10/13 15:13, Peter Schmidt wrote:
> Oh, i got it http://stackoverflow.com/a/5273166/326905
>
> "at least 2 cores and at least 2 GB physical memory"
>
> Until know i'm using a VM with single core and 1GB RAM.
>
> So this will be later for production :)
>
> Thank you Guido.
>
>
> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>
>> Strange. When i add "-server" to the arguments, i got everytime the error
>> on jetty startup
>>
>>
>> Invalid option -server
>> Cannot parse command line arguments
>>
>>
>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>
>>> It is JVM parameter, example:
>>>
>>> JAVA_OPTIONS="-Djava.awt.**headless=true -Dfile.encoding=UTF-8 -server
>>> -Xms256m -Xmx256m"
>>>
>>> If you want to concatenate more JVM parameters you do it like this:
>>> JAVA_OPTIONS="-Dsolr.solr.**home=/usr/share/solr $JAVA_OPTIONS"
>>>
>>> Take a good look at the format,
>>>
>>> Guido.
>>>
>>>
>>> On 11/10/13 13:37, Peter Schmidt wrote:
>>>
>>>> @Guido: Itried it before and than i thought you marked just the server
>>>> options
>>>>
>>>> Because the -sever causes a:
>>>>
>>>> sudo service jetty start
>>>> * Starting Jetty servlet engine.
>>>> jetty
>>>> Invalid option -server
>>>> Cannot parse command line arguments
>>>>
>>>> Or should i substitute server with ...?
>>>>
>>>> Options with -server:
>>>>
>>>>
>>>> JAVA_OPTIONS="-Djava.awt.**headless=true -Dfile.encoding=UTF-8 -server
>>>> -Xms256m -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache
>>>> -Dsolr.solr.home=/usr/share/**solr $JAVA_OPTIONS"
>>>>
>>>>
>>>>
>>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>>
>>>> Remember the "-server" which for Java webapps or dedicated Java services
>>>>> will improve things.
>>>>>
>>>>> Guido.
>>>>>
>>>>>
>>>>> On 11/10/13 12:26, Peter Schmidt wrote:
>>>>>
>>>>> I can report that jetty is running now with this options:
>>>>>> JAVA_OPTIONS="-Djava.awt.****headless=true -Dfile.encoding=UTF-8
>>>>>> -Xms256m
>>>>>>
>>>>>> -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50 -XX:+OptimizeStringConcat
>>>>>> -XX:+UseStringCache -Dsolr.solr.home=/usr/share/****solr
>>>>>> $JAVA_OPTIONS"
>>>>>>
>>>>>>
>>>>>> @Guido: I reduced the min/max heap size to 256m, i will increase this
>>>>>> on
>>>>>> production server.
>>>>>>
>>>>>>
>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>
>>>>>> So the main problem was that the libs must be copied to the
>>>>>> WEB-INF/lib
>>>>>>
>>>>>>> directory insteed of the jetty lib/ext directory. Is the fact that you
>>>>>>> should you use WEB-INF/lib somewhere documented?
>>>>>>>
>>>>>>>
>>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>>
>>>>>>> Not so hard switching it to Oracle JDK 7u40.
>>>>>>>
>>>>>>>> Just download it and change the JAVA_HOME path in
>>>>>>>> /etc/default/jetty, so
>>>>>>>> it's not nescessary to switch java version with
>>>>>>>> update-java-alternatives
>>>>>>>>
>>>>>>>> The machine is 64bit :)
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>>>>>>>
>>>>>>>> Does this work ?
>>>>>>>>
>>>>>>>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>>>>>>>
>>>>>>>>> ???
>>>>>>>>>
>>>>>>>>> Which version of 7 is recommended ?
>>>>>>>>>
>>>>>>>>> Bill Bell
>>>>>>>>> Sent from mobile
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <
>>>>>>>>> dsmiley@mitre.org>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> *Don't* use JDK 7u40, it's been known to cause index corruption and
>>>>>>>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been
>>>>>>>>>> unnoticed
>>>>>>>>>>
>>>>>>>>>> by
>>>>>>>>> Oracle.
>>>>>>>>>> ~ David
>>>>>>>>>>
>>>>>>>>>> On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com>
>>>>>>>>>> wrote:
>>>>>>>>>> 2. Java version: There are huges performance winning between Java
>>>>>>>>>> 5, 6
>>>>>>>>>>
>>>>>>>>>>> and 7; we use Oracle JDK 7u40.
>>>>>>>>>>>
>>>>>>>>>>>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
Oh, i got it http://stackoverflow.com/a/5273166/326905
"at least 2 cores and at least 2 GB physical memory"
Until know i'm using a VM with single core and 1GB RAM.
So this will be later for production :)
Thank you Guido.
2013/10/11 Peter Schmidt <pe...@gmail.com>
> Strange. When i add "-server" to the arguments, i got everytime the error
> on jetty startup
>
>
> Invalid option -server
> Cannot parse command line arguments
>
>
> 2013/10/11 Guido Medina <gu...@temetra.com>
>
>> It is JVM parameter, example:
>>
>> JAVA_OPTIONS="-Djava.awt.**headless=true -Dfile.encoding=UTF-8 -server
>> -Xms256m -Xmx256m"
>>
>> If you want to concatenate more JVM parameters you do it like this:
>> JAVA_OPTIONS="-Dsolr.solr.**home=/usr/share/solr $JAVA_OPTIONS"
>>
>> Take a good look at the format,
>>
>> Guido.
>>
>>
>> On 11/10/13 13:37, Peter Schmidt wrote:
>>
>>> @Guido: Itried it before and than i thought you marked just the server
>>> options
>>>
>>> Because the -sever causes a:
>>>
>>> sudo service jetty start
>>> * Starting Jetty servlet engine.
>>> jetty
>>> Invalid option -server
>>> Cannot parse command line arguments
>>>
>>> Or should i substitute server with ...?
>>>
>>> Options with -server:
>>>
>>>
>>> JAVA_OPTIONS="-Djava.awt.**headless=true -Dfile.encoding=UTF-8 -server
>>> -Xms256m -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>> -XX:+OptimizeStringConcat -XX:+UseStringCache
>>> -Dsolr.solr.home=/usr/share/**solr $JAVA_OPTIONS"
>>>
>>>
>>>
>>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>>
>>> Remember the "-server" which for Java webapps or dedicated Java services
>>>> will improve things.
>>>>
>>>> Guido.
>>>>
>>>>
>>>> On 11/10/13 12:26, Peter Schmidt wrote:
>>>>
>>>> I can report that jetty is running now with this options:
>>>>>
>>>>> JAVA_OPTIONS="-Djava.awt.****headless=true -Dfile.encoding=UTF-8
>>>>> -Xms256m
>>>>>
>>>>> -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50 -XX:+OptimizeStringConcat
>>>>> -XX:+UseStringCache -Dsolr.solr.home=/usr/share/****solr
>>>>> $JAVA_OPTIONS"
>>>>>
>>>>>
>>>>> @Guido: I reduced the min/max heap size to 256m, i will increase this
>>>>> on
>>>>> production server.
>>>>>
>>>>>
>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>
>>>>> So the main problem was that the libs must be copied to the
>>>>> WEB-INF/lib
>>>>>
>>>>>> directory insteed of the jetty lib/ext directory. Is the fact that you
>>>>>> should you use WEB-INF/lib somewhere documented?
>>>>>>
>>>>>>
>>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>>
>>>>>> Not so hard switching it to Oracle JDK 7u40.
>>>>>>
>>>>>>> Just download it and change the JAVA_HOME path in
>>>>>>> /etc/default/jetty, so
>>>>>>> it's not nescessary to switch java version with
>>>>>>> update-java-alternatives
>>>>>>>
>>>>>>> The machine is 64bit :)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>>>>>>
>>>>>>> Does this work ?
>>>>>>>
>>>>>>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>>>>>>
>>>>>>>> ???
>>>>>>>>
>>>>>>>> Which version of 7 is recommended ?
>>>>>>>>
>>>>>>>> Bill Bell
>>>>>>>> Sent from mobile
>>>>>>>>
>>>>>>>>
>>>>>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <
>>>>>>>> dsmiley@mitre.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> *Don't* use JDK 7u40, it's been known to cause index corruption and
>>>>>>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been
>>>>>>>>> unnoticed
>>>>>>>>>
>>>>>>>>> by
>>>>>>>>
>>>>>>>> Oracle.
>>>>>>>>>
>>>>>>>>> ~ David
>>>>>>>>>
>>>>>>>>> On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com>
>>>>>>>>> wrote:
>>>>>>>>> 2. Java version: There are huges performance winning between Java
>>>>>>>>> 5, 6
>>>>>>>>>
>>>>>>>>>> and 7; we use Oracle JDK 7u40.
>>>>>>>>>>
>>>>>>>>>>
>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
Strange. When i add "-server" to the arguments, i got everytime the error
on jetty startup
Invalid option -server
Cannot parse command line arguments
2013/10/11 Guido Medina <gu...@temetra.com>
> It is JVM parameter, example:
>
> JAVA_OPTIONS="-Djava.awt.**headless=true -Dfile.encoding=UTF-8 -server
> -Xms256m -Xmx256m"
>
> If you want to concatenate more JVM parameters you do it like this:
> JAVA_OPTIONS="-Dsolr.solr.**home=/usr/share/solr $JAVA_OPTIONS"
>
> Take a good look at the format,
>
> Guido.
>
>
> On 11/10/13 13:37, Peter Schmidt wrote:
>
>> @Guido: Itried it before and than i thought you marked just the server
>> options
>>
>> Because the -sever causes a:
>>
>> sudo service jetty start
>> * Starting Jetty servlet engine.
>> jetty
>> Invalid option -server
>> Cannot parse command line arguments
>>
>> Or should i substitute server with ...?
>>
>> Options with -server:
>>
>>
>> JAVA_OPTIONS="-Djava.awt.**headless=true -Dfile.encoding=UTF-8 -server
>> -Xms256m -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>> -XX:+OptimizeStringConcat -XX:+UseStringCache
>> -Dsolr.solr.home=/usr/share/**solr $JAVA_OPTIONS"
>>
>>
>>
>> 2013/10/11 Guido Medina <gu...@temetra.com>
>>
>> Remember the "-server" which for Java webapps or dedicated Java services
>>> will improve things.
>>>
>>> Guido.
>>>
>>>
>>> On 11/10/13 12:26, Peter Schmidt wrote:
>>>
>>> I can report that jetty is running now with this options:
>>>>
>>>> JAVA_OPTIONS="-Djava.awt.****headless=true -Dfile.encoding=UTF-8
>>>> -Xms256m
>>>>
>>>> -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50 -XX:+OptimizeStringConcat
>>>> -XX:+UseStringCache -Dsolr.solr.home=/usr/share/****solr $JAVA_OPTIONS"
>>>>
>>>>
>>>> @Guido: I reduced the min/max heap size to 256m, i will increase this on
>>>> production server.
>>>>
>>>>
>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>
>>>> So the main problem was that the libs must be copied to the
>>>> WEB-INF/lib
>>>>
>>>>> directory insteed of the jetty lib/ext directory. Is the fact that you
>>>>> should you use WEB-INF/lib somewhere documented?
>>>>>
>>>>>
>>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>>
>>>>> Not so hard switching it to Oracle JDK 7u40.
>>>>>
>>>>>> Just download it and change the JAVA_HOME path in /etc/default/jetty,
>>>>>> so
>>>>>> it's not nescessary to switch java version with
>>>>>> update-java-alternatives
>>>>>>
>>>>>> The machine is 64bit :)
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>>>>>
>>>>>> Does this work ?
>>>>>>
>>>>>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>>>>>
>>>>>>> ???
>>>>>>>
>>>>>>> Which version of 7 is recommended ?
>>>>>>>
>>>>>>> Bill Bell
>>>>>>> Sent from mobile
>>>>>>>
>>>>>>>
>>>>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <
>>>>>>> dsmiley@mitre.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>> *Don't* use JDK 7u40, it's been known to cause index corruption and
>>>>>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been
>>>>>>>> unnoticed
>>>>>>>>
>>>>>>>> by
>>>>>>>
>>>>>>> Oracle.
>>>>>>>>
>>>>>>>> ~ David
>>>>>>>>
>>>>>>>> On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com>
>>>>>>>> wrote:
>>>>>>>> 2. Java version: There are huges performance winning between Java
>>>>>>>> 5, 6
>>>>>>>>
>>>>>>>>> and 7; we use Oracle JDK 7u40.
>>>>>>>>>
>>>>>>>>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
It is JVM parameter, example:
JAVA_OPTIONS="-Djava.awt.headless=true -Dfile.encoding=UTF-8 -server
-Xms256m -Xmx256m"
If you want to concatenate more JVM parameters you do it like this:
JAVA_OPTIONS="-Dsolr.solr.home=/usr/share/solr $JAVA_OPTIONS"
Take a good look at the format,
Guido.
On 11/10/13 13:37, Peter Schmidt wrote:
> @Guido: Itried it before and than i thought you marked just the server
> options
>
> Because the -sever causes a:
>
> sudo service jetty start
> * Starting Jetty servlet engine.
> jetty
> Invalid option -server
> Cannot parse command line arguments
>
> Or should i substitute server with ...?
>
> Options with -server:
>
>
> JAVA_OPTIONS="-Djava.awt.headless=true -Dfile.encoding=UTF-8 -server
> -Xms256m -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
> -XX:+OptimizeStringConcat -XX:+UseStringCache
> -Dsolr.solr.home=/usr/share/solr $JAVA_OPTIONS"
>
>
>
> 2013/10/11 Guido Medina <gu...@temetra.com>
>
>> Remember the "-server" which for Java webapps or dedicated Java services
>> will improve things.
>>
>> Guido.
>>
>>
>> On 11/10/13 12:26, Peter Schmidt wrote:
>>
>>> I can report that jetty is running now with this options:
>>>
>>> JAVA_OPTIONS="-Djava.awt.**headless=true -Dfile.encoding=UTF-8 -Xms256m
>>> -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50 -XX:+OptimizeStringConcat
>>> -XX:+UseStringCache -Dsolr.solr.home=/usr/share/**solr $JAVA_OPTIONS"
>>>
>>> @Guido: I reduced the min/max heap size to 256m, i will increase this on
>>> production server.
>>>
>>>
>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>
>>> So the main problem was that the libs must be copied to the WEB-INF/lib
>>>> directory insteed of the jetty lib/ext directory. Is the fact that you
>>>> should you use WEB-INF/lib somewhere documented?
>>>>
>>>>
>>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>>
>>>> Not so hard switching it to Oracle JDK 7u40.
>>>>> Just download it and change the JAVA_HOME path in /etc/default/jetty, so
>>>>> it's not nescessary to switch java version with update-java-alternatives
>>>>>
>>>>> The machine is 64bit :)
>>>>>
>>>>>
>>>>>
>>>>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>>>>
>>>>> Does this work ?
>>>>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>>>>
>>>>>> ???
>>>>>>
>>>>>> Which version of 7 is recommended ?
>>>>>>
>>>>>> Bill Bell
>>>>>> Sent from mobile
>>>>>>
>>>>>>
>>>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <ds...@mitre.org>
>>>>>> wrote:
>>>>>>
>>>>>>> *Don't* use JDK 7u40, it's been known to cause index corruption and
>>>>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been unnoticed
>>>>>>>
>>>>>> by
>>>>>>
>>>>>>> Oracle.
>>>>>>>
>>>>>>> ~ David
>>>>>>>
>>>>>>> On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com>
>>>>>>> wrote:
>>>>>>> 2. Java version: There are huges performance winning between Java 5, 6
>>>>>>>> and 7; we use Oracle JDK 7u40.
>>>>>>>>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
@Guido: Itried it before and than i thought you marked just the server
options
Because the -sever causes a:
sudo service jetty start
* Starting Jetty servlet engine.
jetty
Invalid option -server
Cannot parse command line arguments
Or should i substitute server with ...?
Options with -server:
JAVA_OPTIONS="-Djava.awt.headless=true -Dfile.encoding=UTF-8 -server
-Xms256m -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50
-XX:+OptimizeStringConcat -XX:+UseStringCache
-Dsolr.solr.home=/usr/share/solr $JAVA_OPTIONS"
2013/10/11 Guido Medina <gu...@temetra.com>
> Remember the "-server" which for Java webapps or dedicated Java services
> will improve things.
>
> Guido.
>
>
> On 11/10/13 12:26, Peter Schmidt wrote:
>
>> I can report that jetty is running now with this options:
>>
>> JAVA_OPTIONS="-Djava.awt.**headless=true -Dfile.encoding=UTF-8 -Xms256m
>> -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50 -XX:+OptimizeStringConcat
>> -XX:+UseStringCache -Dsolr.solr.home=/usr/share/**solr $JAVA_OPTIONS"
>>
>> @Guido: I reduced the min/max heap size to 256m, i will increase this on
>> production server.
>>
>>
>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>
>> So the main problem was that the libs must be copied to the WEB-INF/lib
>>> directory insteed of the jetty lib/ext directory. Is the fact that you
>>> should you use WEB-INF/lib somewhere documented?
>>>
>>>
>>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>>
>>> Not so hard switching it to Oracle JDK 7u40.
>>>> Just download it and change the JAVA_HOME path in /etc/default/jetty, so
>>>> it's not nescessary to switch java version with update-java-alternatives
>>>>
>>>> The machine is 64bit :)
>>>>
>>>>
>>>>
>>>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>>>
>>>> Does this work ?
>>>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>>>
>>>>> ???
>>>>>
>>>>> Which version of 7 is recommended ?
>>>>>
>>>>> Bill Bell
>>>>> Sent from mobile
>>>>>
>>>>>
>>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <ds...@mitre.org>
>>>>>>
>>>>> wrote:
>>>>>
>>>>>> *Don't* use JDK 7u40, it's been known to cause index corruption and
>>>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been unnoticed
>>>>>>
>>>>> by
>>>>>
>>>>>> Oracle.
>>>>>>
>>>>>> ~ David
>>>>>>
>>>>>> On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com>
>>>>>>>
>>>>>> wrote:
>>>>>
>>>>>> 2. Java version: There are huges performance winning between Java 5, 6
>>>>>>> and 7; we use Oracle JDK 7u40.
>>>>>>>
>>>>>>
>>>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
Remember the "-server" which for Java webapps or dedicated Java services
will improve things.
Guido.
On 11/10/13 12:26, Peter Schmidt wrote:
> I can report that jetty is running now with this options:
>
> JAVA_OPTIONS="-Djava.awt.headless=true -Dfile.encoding=UTF-8 -Xms256m
> -Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50 -XX:+OptimizeStringConcat
> -XX:+UseStringCache -Dsolr.solr.home=/usr/share/solr $JAVA_OPTIONS"
>
> @Guido: I reduced the min/max heap size to 256m, i will increase this on
> production server.
>
>
> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>
>> So the main problem was that the libs must be copied to the WEB-INF/lib
>> directory insteed of the jetty lib/ext directory. Is the fact that you
>> should you use WEB-INF/lib somewhere documented?
>>
>>
>> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>>
>>> Not so hard switching it to Oracle JDK 7u40.
>>> Just download it and change the JAVA_HOME path in /etc/default/jetty, so
>>> it's not nescessary to switch java version with update-java-alternatives
>>>
>>> The machine is 64bit :)
>>>
>>>
>>>
>>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>>
>>>> Does this work ?
>>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>>
>>>> ???
>>>>
>>>> Which version of 7 is recommended ?
>>>>
>>>> Bill Bell
>>>> Sent from mobile
>>>>
>>>>
>>>>> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <ds...@mitre.org>
>>>> wrote:
>>>>> *Don't* use JDK 7u40, it's been known to cause index corruption and
>>>>> SIGSEGV faults with Lucene: LUCENE-5212 This has not been unnoticed
>>>> by
>>>>> Oracle.
>>>>>
>>>>> ~ David
>>>>>
>>>>>> On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com>
>>>> wrote:
>>>>>> 2. Java version: There are huges performance winning between Java 5, 6
>>>>>> and 7; we use Oracle JDK 7u40.
>>>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
I can report that jetty is running now with this options:
JAVA_OPTIONS="-Djava.awt.headless=true -Dfile.encoding=UTF-8 -Xms256m
-Xmx256m -XX:+UseG1GC -XX:MaxGCPauseMillis=50 -XX:+OptimizeStringConcat
-XX:+UseStringCache -Dsolr.solr.home=/usr/share/solr $JAVA_OPTIONS"
@Guido: I reduced the min/max heap size to 256m, i will increase this on
production server.
2013/10/11 Peter Schmidt <pe...@gmail.com>
> So the main problem was that the libs must be copied to the WEB-INF/lib
> directory insteed of the jetty lib/ext directory. Is the fact that you
> should you use WEB-INF/lib somewhere documented?
>
>
> 2013/10/11 Peter Schmidt <pe...@gmail.com>
>
>> Not so hard switching it to Oracle JDK 7u40.
>> Just download it and change the JAVA_HOME path in /etc/default/jetty, so
>> it's not nescessary to switch java version with update-java-alternatives
>>
>> The machine is 64bit :)
>>
>>
>>
>> 2013/10/11 Bill Bell <bi...@gmail.com>
>>
>>> Does this work ?
>>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>>
>>> ???
>>>
>>> Which version of 7 is recommended ?
>>>
>>> Bill Bell
>>> Sent from mobile
>>>
>>>
>>> > On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <ds...@mitre.org>
>>> wrote:
>>> >
>>> > *Don't* use JDK 7u40, it's been known to cause index corruption and
>>> > SIGSEGV faults with Lucene: LUCENE-5212 This has not been unnoticed
>>> by
>>> > Oracle.
>>> >
>>> > ~ David
>>> >
>>> >> On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com>
>>> wrote:
>>> >>
>>> >> 2. Java version: There are huges performance winning between Java 5, 6
>>> >> and 7; we use Oracle JDK 7u40.
>>> >
>>>
>>
>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Shawn Heisey <so...@elyograg.org>.
On 10/11/2013 4:55 AM, Peter Schmidt wrote:
> So the main problem was that the libs must be copied to the WEB-INF/lib
> directory insteed of the jetty lib/ext directory. Is the fact that you
> should you use WEB-INF/lib somewhere documented?
Actually, jetty's lib/ext is preferred, modifying the .war file is NOT
recommended.
Solr used to ship with the logging jars in the .war file, similar to the
result that Guido's procedure gives you.
http://wiki.apache.org/solr/SolrLogging#What_changed
This was changed in version 4.3.0 because many people were having to
take manual steps to change logging frameworks. There is a strong
preference among people who really care about logging for using log4j or
logback instead of java.util.logging. Now nobody needs to compile Solr
themselves or perform surgery on the .war file when they want to change
their logging, and the default produces much better results.
Thanks,
Shawn
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
So the main problem was that the libs must be copied to the WEB-INF/lib
directory insteed of the jetty lib/ext directory. Is the fact that you
should you use WEB-INF/lib somewhere documented?
2013/10/11 Peter Schmidt <pe...@gmail.com>
> Not so hard switching it to Oracle JDK 7u40.
> Just download it and change the JAVA_HOME path in /etc/default/jetty, so
> it's not nescessary to switch java version with update-java-alternatives
>
> The machine is 64bit :)
>
>
>
> 2013/10/11 Bill Bell <bi...@gmail.com>
>
>> Does this work ?
>> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>>
>> ???
>>
>> Which version of 7 is recommended ?
>>
>> Bill Bell
>> Sent from mobile
>>
>>
>> > On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <ds...@mitre.org>
>> wrote:
>> >
>> > *Don't* use JDK 7u40, it's been known to cause index corruption and
>> > SIGSEGV faults with Lucene: LUCENE-5212 This has not been unnoticed by
>> > Oracle.
>> >
>> > ~ David
>> >
>> >> On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com> wrote:
>> >>
>> >> 2. Java version: There are huges performance winning between Java 5, 6
>> >> and 7; we use Oracle JDK 7u40.
>> >
>>
>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
Not so hard switching it to Oracle JDK 7u40.
Just download it and change the JAVA_HOME path in /etc/default/jetty, so
it's not nescessary to switch java version with update-java-alternatives
The machine is 64bit :)
2013/10/11 Bill Bell <bi...@gmail.com>
> Does this work ?
> I can suggest -XX:-UseLoopPredicate to switch off predicates.
>
> ???
>
> Which version of 7 is recommended ?
>
> Bill Bell
> Sent from mobile
>
>
> > On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <ds...@mitre.org>
> wrote:
> >
> > *Don't* use JDK 7u40, it's been known to cause index corruption and
> > SIGSEGV faults with Lucene: LUCENE-5212 This has not been unnoticed by
> > Oracle.
> >
> > ~ David
> >
> >> On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com> wrote:
> >>
> >> 2. Java version: There are huges performance winning between Java 5, 6
> >> and 7; we use Oracle JDK 7u40.
> >
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Bill Bell <bi...@gmail.com>.
Does this work ?
I can suggest -XX:-UseLoopPredicate to switch off predicates.
???
Which version of 7 is recommended ?
Bill Bell
Sent from mobile
> On Oct 10, 2013, at 11:29 AM, "Smiley, David W." <ds...@mitre.org> wrote:
>
> *Don't* use JDK 7u40, it's been known to cause index corruption and
> SIGSEGV faults with Lucene: LUCENE-5212 This has not been unnoticed by
> Oracle.
>
> ~ David
>
>> On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com> wrote:
>>
>> 2. Java version: There are huges performance winning between Java 5, 6
>> and 7; we use Oracle JDK 7u40.
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
Hmm, thanks for sharing this, according to the JIRA comments it seems to
affect only 32 bits systems?
https://issues.apache.org/jira/browse/LUCENE-5212
Guido.
On 10/10/13 18:29, Smiley, David W. wrote:
> *Don't* use JDK 7u40, it's been known to cause index corruption and
> SIGSEGV faults with Lucene: LUCENE-5212 This has not been unnoticed by
> Oracle.
>
> ~ David
>
> On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com> wrote:
>
>> 2. Java version: There are huges performance winning between Java 5, 6
>> and 7; we use Oracle JDK 7u40.
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package
Repository
Posted by "Smiley, David W." <ds...@mitre.org>.
*Don't* use JDK 7u40, it's been known to cause index corruption and
SIGSEGV faults with Lucene: LUCENE-5212 This has not been unnoticed by
Oracle.
~ David
On 10/10/13 12:34 PM, "Guido Medina" <gu...@temetra.com> wrote:
>2. Java version: There are huges performance winning between Java 5, 6
> and 7; we use Oracle JDK 7u40.
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
Even if you use a newer jetty, you won't see any difference, what you
should care:
1. Jetty using NIO which is enabled by default on Jetty coming from
Ubuntu repo (I think)
2. Java version: There are huges performance winning between Java 5, 6
and 7; we use Oracle JDK 7u40.
3. JVM options for GC, -server flag, etc, the JAVA_OPTIONS I sent
before are the ones we are using on production.
4. Solrconfig.xml: Things like caches (initial size, size, etc),
softcommit, autocommit, but that's the next step I guess.
Guido.
On 10/10/13 17:27, Guido Medina wrote:
> Why not just go straight for 4.5.0? Also, we have it running with JDK
> 7, we use Oracle's JVM sym-linked to /opt/java, that would be an extra
> step (modifying the JAVA_HOME at /etc/defaul/jetty), it it worthy doing.
>
> Glad I helped, cheers,
>
> Guido.
>
> On 10/10/13 16:57, Peter Schmidt wrote:
>> SOLVED: I reinstalled the jetty package, because i wanted to get a clean
>> installation. And now it's working with your hint Guido :-) Thank you
>> very
>> much.
>>
>> What i did:
>>
>> # Download Solr
>> wget http://archive.apache.org/dist/lucene/solr/4.4.0/solr-4.4.0.tgz
>> tar xvfz solr-4.4.0.tgz
>>
>> # Extract content from solr.war and add missing jars from the lib/ext
>> like
>> Guido described
>> mkdir dir_to_extract
>> cp -R solr-4.4.0/example/webapps/solr.war dir_to_extract
>> cd dir_to_extract
>> unzip solr.war
>> rm solr.war
>> cp ../solr-4.4.0/example/lib/ext/*.jar WEB-INF/lib/
>> jar -cvf solr.war *
>>
>> # copy new var to jetty webapps folder
>> sudo cp solr.war /usr/share/jetty/webapps
>>
>> # Copy Solr example files
>> sudo mkdir /usr/share/solr
>> sudo cp -R solr-4.4.0/example/* /usr/share/solr/
>> sudo chmod -R jetty:adm /usr/share/solr
>>
>> # Edit jetty config
>> vi /etc/default/jetty
>>
>> NO_START=0
>> VERBOSE=yes
>> JETTY_HOST=0.0.0.0
>> JAVA_OPTIONS="-Xmx256m -Djava.awt.headless=true
>> -Dsolr.solr.home=/usr/share/solr/solr $JAVA_OPTIONS"
>>
>> And then Solr 4.4.0 is accessible on http://localhost:8080/solr
>>
>> But i also saw the box with the hint on
>> https://cwiki.apache.org/confluence/display/solr/Installing+Solr:
>>
>> "Solr ships with a working Jetty server, with optimized settings for
>> Solr,
>> inside the example directory. It is recommended that you use the
>> provided
>> Jetty server for optimal performance. If you absolutely must use a
>> different servlet container then continue to the next section on how to
>> install Solr."
>>
>> @Guido: Do you know if the performance is weaker with the Jetty 6.1?
>>
>> And which Jetty version is the inluded one?
>>
>>
>>
>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>
>>> i added the jars you have listet and recreated a solr.war
>>>
>>>
>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>
>>>> OK. I extracted the solr.war in webapps folder. And than out.log
>>>> reports
>>>>
>>>> 2013-10-10 16:47:28.184:WARN::Config error at <New id="ServerLog"
>>>> class="java.io.PrintStream"><Arg>| <New
>>>> class="org.mortbay.util.RolloverFileOutputStream"><Arg><SystemProperty
>>>> name="jetty.home"
>>>> default="."/>/logs/yyyy_mm_dd.stderrout.log</Arg><Arg
>>>> type="boolean">false</Arg><Arg type="int">90</Arg><Arg><Call
>>>> class="java.util.TimeZone"
>>>> name="getTimeZone"><Arg>GMT</Arg></Call></Arg><Get id="ServerLogName"
>>>> name="datedFilename"/></New>| </Arg></New>
>>>> java.lang.reflect.InvocationTargetException
>>>> 2013-10-10 16:47:28.191:WARN::EXCEPTION
>>>> java.lang.reflect.InvocationTargetException
>>>>
>>>> at
>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>>> Method)
>>>> at
>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>>>
>>>> at
>>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>>>
>>>> at
>>>> java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:608)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:915)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:837)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:593)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:256)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>> Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>> at org.mortbay.start.Main.invokeMain(Main.java:194)
>>>> at org.mortbay.start.Main.start(Main.java:534)
>>>> at
>>>> org.mortbay.jetty.start.daemon.Bootstrap.start(Bootstrap.java:30)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>> Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>> at
>>>> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
>>>>
>>>> 2013-10-10 16:47:28.192:WARN::Nested in
>>>> java.lang.reflect.InvocationTargetException:
>>>> java.io.IOException: Cannot write log file
>>>> /var/log/jetty/2013_10_10.stderrout.log
>>>> at
>>>> org.mortbay.util.RolloverFileOutputStream.setFile(RolloverFileOutputStream.java:233)
>>>>
>>>> at
>>>> org.mortbay.util.RolloverFileOutputStream.<init>(RolloverFileOutputStream.java:164)
>>>>
>>>> at
>>>> org.mortbay.util.RolloverFileOutputStream.<init>(RolloverFileOutputStream.java:116)
>>>>
>>>>
>>>> at
>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>>> Method)
>>>> at
>>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>>>
>>>> at
>>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>>>
>>>> at
>>>> java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:608)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:915)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:837)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:593)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:256)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
>>>> at
>>>> org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>> Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>> at org.mortbay.start.Main.invokeMain(Main.java:194)
>>>> at org.mortbay.start.Main.start(Main.java:534)
>>>> at
>>>> org.mortbay.jetty.start.daemon.Bootstrap.start(Bootstrap.java:30)
>>>>
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>>> Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>>>
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>>
>>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>>> at
>>>> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
>>>>
>>>>
>>>>
>>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>>
>>>>> Add the following jars inside solr.war WEB-INF/lib folder:
>>>>>
>>>>> jcl-over-slf4j-1.7.5.jar
>>>>> jul-to-slf4j-1.7.5.jar
>>>>> log4j-1.2.17.jar
>>>>> slf4j-api-1.7.5.jar
>>>>> slf4j-log4j12-1.7.5.jar
>>>>>
>>>>> Optional if you are going to use spatial search:
>>>>> jts-1.13.jar
>>>>>
>>>>> Guido.
>>>>>
>>>>>
>>>>> On 10/10/13 14:33, Peter Schmidt wrote:
>>>>>
>>>>>> Sorry terminal shows:
>>>>>>
>>>>>> $ sudo service jetty start
>>>>>> Found JAVA=/usr/lib/jvm/java-6-**openjdk/jre/bin/java in JAVA_HOME=/
>>>>>> Starting Jetty: FAILED
>>>>>>
>>>>>>
>>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>>
>>>>>> The log:
>>>>>>> 2013-10-10 15:01:47.071:INFO::jetty-6.1.**22
>>>>>>> 2013-10-10 15:01:47.110:INFO::Deploy
>>>>>>> /etc/jetty/contexts/javadoc.**xml
>>>>>>> ->
>>>>>>> org.mortbay.jetty.handler.**ContextHandler@2353f67e
>>>>>>> {/javadoc,file:/usr/share/doc/**libjetty-java/api/}
>>>>>>> 2013-10-10 15:01:47.161:INFO::NO JSP Support for , did not find
>>>>>>> org.apache.jasper.servlet.**JspServlet
>>>>>>> 2013-10-10 15:01:47.192:INFO::Extract
>>>>>>> file:/var/lib/jetty/webapps/**
>>>>>>> solr.war
>>>>>>> to /tmp/Jetty_0_0_0_0_8080_solr.**war__solr__7k9npr/webapp
>>>>>>> 2013-10-10 15:01:47.761:INFO::NO JSP Support for /solr, did not
>>>>>>> find
>>>>>>> org.apache.jasper.servlet.**JspServlet
>>>>>>> 2013-10-10 15:01:47.868:WARN::failed SolrRequestFilter:
>>>>>>> org.apache.solr.common.**SolrException: Could not find necessary
>>>>>>> SLF4j
>>>>>>> logging jars. If using Jetty, the SLF4j logging jars need to go
>>>>>>> in the
>>>>>>> jetty lib/ext directory. For other containers, the corresponding
>>>>>>> directory
>>>>>>> should be used. For more information, see:
>>>>>>> http://wiki.apache.org/solr/**SolrLogging<http://wiki.apache.org/solr/SolrLogging>
>>>>>>>
>>>>>>> 2013-10-10 15:01:47.869:WARN::Failed startup of context
>>>>>>> org.mortbay.jetty.webapp.**WebAppContext@a13f991
>>>>>>> {/solr,file:/var/lib/jetty/**webapps/solr.war}
>>>>>>> org.apache.solr.common.**SolrException: Could not find necessary
>>>>>>> SLF4j
>>>>>>> logging jars. If using Jetty, the SLF4j logging jars need to go
>>>>>>> in the
>>>>>>> jetty lib/ext directory. For other containers, the corresponding
>>>>>>> directory
>>>>>>> should be used. For more information, see:
>>>>>>> http://wiki.apache.org/solr/**SolrLogging<http://wiki.apache.org/solr/SolrLogging>
>>>>>>>
>>>>>>> at
>>>>>>> org.apache.solr.servlet.**SolrDispatchFilter.<init>(**
>>>>>>> SolrDispatchFilter.java:104)
>>>>>>> at sun.reflect.**NativeConstructorAccessorImpl.**
>>>>>>> newInstance0(Native
>>>>>>> Method)
>>>>>>> at
>>>>>>> sun.reflect.**NativeConstructorAccessorImpl.**newInstance(**
>>>>>>> NativeConstructorAccessorImpl.**java:57)
>>>>>>> at
>>>>>>> sun.reflect.**DelegatingConstructorAccessorI**mpl.newInstance(**
>>>>>>> DelegatingConstructorAccessorI**mpl.java:45)
>>>>>>> at java.lang.reflect.Constructor.**
>>>>>>> newInstance(Constructor.java:**532)
>>>>>>> at java.lang.Class.newInstance0(**Class.java:374)
>>>>>>> at java.lang.Class.newInstance(**Class.java:327)
>>>>>>> at
>>>>>>> org.mortbay.jetty.servlet.**Holder.newInstance(Holder.**
>>>>>>> java:153)
>>>>>>> at
>>>>>>> org.mortbay.jetty.servlet.**FilterHolder.doStart(**
>>>>>>> FilterHolder.java:92)
>>>>>>> at
>>>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>>>> AbstractLifeCycle.java:50)
>>>>>>> at
>>>>>>> org.mortbay.jetty.servlet.**ServletHandler.initialize(**
>>>>>>> ServletHandler.java:662)
>>>>>>> at
>>>>>>> org.mortbay.jetty.servlet.**Context.startContext(Context.*
>>>>>>> *java:140)
>>>>>>> at
>>>>>>> org.mortbay.jetty.webapp.**WebAppContext.startContext(**
>>>>>>> WebAppContext.java:1250)
>>>>>>> at
>>>>>>> org.mortbay.jetty.handler.**ContextHandler.doStart(**
>>>>>>> ContextHandler.java:518)
>>>>>>> at
>>>>>>> org.mortbay.jetty.webapp.**WebAppContext.doStart(**
>>>>>>> WebAppContext.java:467)
>>>>>>> at
>>>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>>>> AbstractLifeCycle.java:50)
>>>>>>> at
>>>>>>> org.mortbay.jetty.handler.**HandlerCollection.doStart(**
>>>>>>> HandlerCollection.java:152)
>>>>>>> at
>>>>>>> org.mortbay.jetty.handler.**ContextHandlerCollection.**doStart(**
>>>>>>> ContextHandlerCollection.java:**156)
>>>>>>> at
>>>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>>>> AbstractLifeCycle.java:50)
>>>>>>> at
>>>>>>> org.mortbay.jetty.handler.**HandlerCollection.doStart(**
>>>>>>> HandlerCollection.java:152)
>>>>>>> at
>>>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>>>> AbstractLifeCycle.java:50)
>>>>>>> at
>>>>>>> org.mortbay.jetty.handler.**HandlerWrapper.doStart(**
>>>>>>> HandlerWrapper.java:130)
>>>>>>> at org.mortbay.jetty.Server.**doStart(Server.java:224)
>>>>>>> at
>>>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>>>> AbstractLifeCycle.java:50)
>>>>>>> at org.mortbay.xml.**XmlConfiguration.main(**
>>>>>>> XmlConfiguration.java:985)
>>>>>>> at
>>>>>>> sun.reflect.**NativeMethodAccessorImpl.**invoke0(Native
>>>>>>> Method)
>>>>>>> at
>>>>>>> sun.reflect.**NativeMethodAccessorImpl.**invoke(**
>>>>>>> NativeMethodAccessorImpl.java:**57)
>>>>>>> at
>>>>>>> sun.reflect.**DelegatingMethodAccessorImpl.**invoke(**
>>>>>>> DelegatingMethodAccessorImpl.**java:43)
>>>>>>> at java.lang.reflect.Method.**invoke(Method.java:616)
>>>>>>> at org.mortbay.start.Main.**invokeMain(Main.java:194)
>>>>>>> at org.mortbay.start.Main.start(**Main.java:534)
>>>>>>> at org.mortbay.start.Main.start(**Main.java:441)
>>>>>>> at org.mortbay.start.Main.main(**Main.java:119)
>>>>>>> 2013-10-10 15:01:47.870:WARN::failed
>>>>>>> org.mortbay.jetty.webapp.**WebAppContext@a13f991{/solr,**
>>>>>>> file:/var/lib/jetty/webapps/**solr.war}:
>>>>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>>>>> 2013-10-10 15:01:47.870:WARN::failed ContextHandlerCollection@**
>>>>>>> 2565a3c2:
>>>>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>>>>> 2013-10-10 15:01:47.870:INFO::Opened /var/log/jetty/2013_10_10.**
>>>>>>> request.log
>>>>>>> 2013-10-10 15:01:47.871:WARN::failed HandlerCollection@33e228bc:
>>>>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>>>>> 2013-10-10 15:01:47.871:WARN::Error starting handlers
>>>>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>>>>> at java.lang.Class.**getDeclaredMethods0(Native Method)
>>>>>>> at java.lang.Class.**privateGetDeclaredMethods(**
>>>>>>> Class.java:2482)
>>>>>>> at java.lang.Class.getMethod0(**Class.java:2725)
>>>>>>> at java.lang.Class.getMethod(**Class.java:1650)
>>>>>>> at org.mortbay.log.Log.unwind(**Log.java:228)
>>>>>>> at org.mortbay.log.Log.warn(Log.**java:197)
>>>>>>> at
>>>>>>> org.mortbay.jetty.webapp.**WebAppContext.doStart(**
>>>>>>> WebAppContext.java:475)
>>>>>>> ...
>>>>>>>
>>>>>>> And when i copy the jars from solr-4.4.0/example/lib and
>>>>>>> solr-4.4.0/example/lib and solr-4.4.0/example/lib/ext to jettys lib
>>>>>>> directory and lib/ext the server is not starting anymore. Quits
>>>>>>> with
>>>>>>> JETTY:
>>>>>>> Failed without logging something
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>>>>>
>>>>>>> Check the jetty logs, there must be something wrong in your
>>>>>>> collection
>>>>>>>> config, usually if it doesn't start it will tell you there.
>>>>>>>>
>>>>>>>> And of course, for every change you make be sure you restart
>>>>>>>> jetty.
>>>>>>>>
>>>>>>>> Guido.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 10/10/13 13:20, Peter Schmidt wrote:
>>>>>>>>
>>>>>>>> No, it's not working that easy with the jetty 6.1.
>>>>>>>>> When i just add -Dsolr.solr.home to my /etc/default/jetty and
>>>>>>>>> put the
>>>>>>>>> solr.war in the jetty webapps directory i got a 404 when in
>>>>>>>>> try to
>>>>>>>>> reach
>>>>>>>>> http://localhost:8080 or http://localhost:8080/solr.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>>>>>>>
>>>>>>>>> My I forgot to mention where you need to copy the solr.war
>>>>>>>>> file:
>>>>>>>>>
>>>>>>>>>> /var/lib/jetty/webapps
>>>>>>>>>>
>>>>>>>>>> Guido.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On 10/10/13 10:48, Guido Medina wrote:
>>>>>>>>>>
>>>>>>>>>> Here is the pertinent changes you need to pass to
>>>>>>>>>> /etc/default/jetty:
>>>>>>>>>>
>>>>>>>>>>> * JAVA_OPTIONS="-Djava.awt.******headless=true
>>>>>>>>>>> -Dfile.encoding=UTF-8
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> -server -Xms8g -Xmx8g -XX:+UseG1GC
>>>>>>>>>>> -XX:MaxGCPauseMillis=50
>>>>>>>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>>>>>>>>>>> * JAVA_OPTIONS="-Dsolr.solr.******
>>>>>>>>>>> home=$YOUR_SOLR_COLLECTION_******HOME
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> $JAVA_OPTIONS"
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are
>>>>>>>>>>> free to
>>>>>>>>>>> play
>>>>>>>>>>> with it. Adjust your solr collection home to whatever path
>>>>>>>>>>> is on
>>>>>>>>>>> your
>>>>>>>>>>> system.
>>>>>>>>>>>
>>>>>>>>>>> HTH,
>>>>>>>>>>>
>>>>>>>>>>> Guido.
>>>>>>>>>>>
>>>>>>>>>>> On 10/10/13 10:43, Guido Medina wrote:
>>>>>>>>>>>
>>>>>>>>>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from
>>>>>>>>>>> Ubuntu
>>>>>>>>>>>
>>>>>>>>>>>> repo, we have in production for few years now with no
>>>>>>>>>>>> issues, you
>>>>>>>>>>>> just need
>>>>>>>>>>>> to be sure your solr.war has the required jars in it, also
>>>>>>>>>>>> your
>>>>>>>>>>>> collection
>>>>>>>>>>>> must have the extra jars needed by your app.
>>>>>>>>>>>>
>>>>>>>>>>>> We have been running it in Ubuntu Server 12.04 LTS for a long
>>>>>>>>>>>> time, it
>>>>>>>>>>>> is easy to have the jetty server with default repo package
>>>>>>>>>>>> since
>>>>>>>>>>>> it
>>>>>>>>>>>> is easy
>>>>>>>>>>>> to pass JVM parameters using /etc/default/jetty config file.
>>>>>>>>>>>>
>>>>>>>>>>>> HTH,
>>>>>>>>>>>>
>>>>>>>>>>>> Guido.
>>>>>>>>>>>>
>>>>>>>>>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> Do you get an error?
>>>>>>>>>>>>
>>>>>>>>>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hey folks,
>>>>>>>>>>>>>
>>>>>>>>>>>>> for some days i tried to get Solr 4.4.0 working as a
>>>>>>>>>>>>> webapp with
>>>>>>>>>>>>>> Jetty
>>>>>>>>>>>>>> 6.1
>>>>>>>>>>>>>> from the Ubuntu repository installed with apt-get. First i
>>>>>>>>>>>>>> tried the
>>>>>>>>>>>>>> installation according the wiki
>>>>>>>>>>>>>> http://wiki.apache.org/solr/**
>>>>>>>>>>>>>> SolrJetty
>>>>>>>>>>>>>> <http://wiki.apache.org/solr/****SolrJetty<http://wiki.apache.org/solr/**SolrJetty>
>>>>>>>>>>>>>> <http://wiki.apache.**org/solr/SolrJetty<http://wiki.apache.org/solr/SolrJetty>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> .
>>>>>>>>>>>>>> Then
>>>>>>>>>>>>>> i found this example
>>>>>>>>>>>>>> http://www.kingstonlabs.com/******blog/how-to-install-solr-36-*
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ***<http://www.kingstonlabs.com/****blog/how-to-install-solr-36-**>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> <http://www.kingstonlabs.**com/**blog/how-to-install-**
>>>>>>>>>>>>>> solr-36-**<http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> on-ubuntu-1204/and<http://www.****kingstonlabs.com/blog/how-**
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> to-** <http://kingstonlabs.com/blog/how-to-**>
>>>>>>>>>>>>>> install-solr-36-on-ubuntu-****1204/and<http://www.**
>>>>>>>>>>>>>> kingstonlabs.com/blog/how-to-**install-solr-36-on-ubuntu-**
>>>>>>>>>>>>>> 1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> tried the Configuration according to the book pache Solr 4
>>>>>>>>>>>>>> Cookbook
>>>>>>>>>>>>>> by
>>>>>>>>>>>>>> Rafal Kuc.
>>>>>>>>>>>>>> But it semmed to be impossible to run Solr 4.4.0 as
>>>>>>>>>>>>>> webapp on
>>>>>>>>>>>>>> Ubuntus
>>>>>>>>>>>>>> jetty 6.1 :(
>>>>>>>>>>>>>> Can somebody confirm that it's impossible or give me an
>>>>>>>>>>>>>> advice
>>>>>>>>>>>>>> how
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>> run
>>>>>>>>>>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
Why not just go straight for 4.5.0? Also, we have it running with JDK 7,
we use Oracle's JVM sym-linked to /opt/java, that would be an extra step
(modifying the JAVA_HOME at /etc/defaul/jetty), it it worthy doing.
Glad I helped, cheers,
Guido.
On 10/10/13 16:57, Peter Schmidt wrote:
> SOLVED: I reinstalled the jetty package, because i wanted to get a clean
> installation. And now it's working with your hint Guido :-) Thank you very
> much.
>
> What i did:
>
> # Download Solr
> wget http://archive.apache.org/dist/lucene/solr/4.4.0/solr-4.4.0.tgz
> tar xvfz solr-4.4.0.tgz
>
> # Extract content from solr.war and add missing jars from the lib/ext like
> Guido described
> mkdir dir_to_extract
> cp -R solr-4.4.0/example/webapps/solr.war dir_to_extract
> cd dir_to_extract
> unzip solr.war
> rm solr.war
> cp ../solr-4.4.0/example/lib/ext/*.jar WEB-INF/lib/
> jar -cvf solr.war *
>
> # copy new var to jetty webapps folder
> sudo cp solr.war /usr/share/jetty/webapps
>
> # Copy Solr example files
> sudo mkdir /usr/share/solr
> sudo cp -R solr-4.4.0/example/* /usr/share/solr/
> sudo chmod -R jetty:adm /usr/share/solr
>
> # Edit jetty config
> vi /etc/default/jetty
>
> NO_START=0
> VERBOSE=yes
> JETTY_HOST=0.0.0.0
> JAVA_OPTIONS="-Xmx256m -Djava.awt.headless=true
> -Dsolr.solr.home=/usr/share/solr/solr $JAVA_OPTIONS"
>
> And then Solr 4.4.0 is accessible on http://localhost:8080/solr
>
> But i also saw the box with the hint on
> https://cwiki.apache.org/confluence/display/solr/Installing+Solr:
>
> "Solr ships with a working Jetty server, with optimized settings for Solr,
> inside the example directory. It is recommended that you use the provided
> Jetty server for optimal performance. If you absolutely must use a
> different servlet container then continue to the next section on how to
> install Solr."
>
> @Guido: Do you know if the performance is weaker with the Jetty 6.1?
>
> And which Jetty version is the inluded one?
>
>
>
> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>
>> i added the jars you have listet and recreated a solr.war
>>
>>
>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>
>>> OK. I extracted the solr.war in webapps folder. And than out.log reports
>>>
>>> 2013-10-10 16:47:28.184:WARN::Config error at <New id="ServerLog"
>>> class="java.io.PrintStream"><Arg>| <New
>>> class="org.mortbay.util.RolloverFileOutputStream"><Arg><SystemProperty
>>> name="jetty.home" default="."/>/logs/yyyy_mm_dd.stderrout.log</Arg><Arg
>>> type="boolean">false</Arg><Arg type="int">90</Arg><Arg><Call
>>> class="java.util.TimeZone"
>>> name="getTimeZone"><Arg>GMT</Arg></Call></Arg><Get id="ServerLogName"
>>> name="datedFilename"/></New>| </Arg></New>
>>> java.lang.reflect.InvocationTargetException
>>> 2013-10-10 16:47:28.191:WARN::EXCEPTION
>>> java.lang.reflect.InvocationTargetException
>>>
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>> Method)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>>> at
>>> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:608)
>>> at
>>> org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:915)
>>> at
>>> org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:837)
>>> at
>>> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:593)
>>> at
>>> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:256)
>>> at
>>> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
>>> at
>>> org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>> at org.mortbay.start.Main.invokeMain(Main.java:194)
>>> at org.mortbay.start.Main.start(Main.java:534)
>>> at
>>> org.mortbay.jetty.start.daemon.Bootstrap.start(Bootstrap.java:30)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>> at
>>> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
>>> 2013-10-10 16:47:28.192:WARN::Nested in
>>> java.lang.reflect.InvocationTargetException:
>>> java.io.IOException: Cannot write log file
>>> /var/log/jetty/2013_10_10.stderrout.log
>>> at
>>> org.mortbay.util.RolloverFileOutputStream.setFile(RolloverFileOutputStream.java:233)
>>> at
>>> org.mortbay.util.RolloverFileOutputStream.<init>(RolloverFileOutputStream.java:164)
>>> at
>>> org.mortbay.util.RolloverFileOutputStream.<init>(RolloverFileOutputStream.java:116)
>>>
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>> Method)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>>> at
>>> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:608)
>>> at
>>> org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:915)
>>> at
>>> org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:837)
>>> at
>>> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:593)
>>> at
>>> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:256)
>>> at
>>> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
>>> at
>>> org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>> at org.mortbay.start.Main.invokeMain(Main.java:194)
>>> at org.mortbay.start.Main.start(Main.java:534)
>>> at
>>> org.mortbay.jetty.start.daemon.Bootstrap.start(Bootstrap.java:30)
>>>
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:616)
>>> at
>>> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
>>>
>>>
>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>
>>>> Add the following jars inside solr.war WEB-INF/lib folder:
>>>>
>>>> jcl-over-slf4j-1.7.5.jar
>>>> jul-to-slf4j-1.7.5.jar
>>>> log4j-1.2.17.jar
>>>> slf4j-api-1.7.5.jar
>>>> slf4j-log4j12-1.7.5.jar
>>>>
>>>> Optional if you are going to use spatial search:
>>>> jts-1.13.jar
>>>>
>>>> Guido.
>>>>
>>>>
>>>> On 10/10/13 14:33, Peter Schmidt wrote:
>>>>
>>>>> Sorry terminal shows:
>>>>>
>>>>> $ sudo service jetty start
>>>>> Found JAVA=/usr/lib/jvm/java-6-**openjdk/jre/bin/java in JAVA_HOME=/
>>>>> Starting Jetty: FAILED
>>>>>
>>>>>
>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>
>>>>> The log:
>>>>>> 2013-10-10 15:01:47.071:INFO::jetty-6.1.**22
>>>>>> 2013-10-10 15:01:47.110:INFO::Deploy /etc/jetty/contexts/javadoc.**xml
>>>>>> ->
>>>>>> org.mortbay.jetty.handler.**ContextHandler@2353f67e
>>>>>> {/javadoc,file:/usr/share/doc/**libjetty-java/api/}
>>>>>> 2013-10-10 15:01:47.161:INFO::NO JSP Support for , did not find
>>>>>> org.apache.jasper.servlet.**JspServlet
>>>>>> 2013-10-10 15:01:47.192:INFO::Extract file:/var/lib/jetty/webapps/**
>>>>>> solr.war
>>>>>> to /tmp/Jetty_0_0_0_0_8080_solr.**war__solr__7k9npr/webapp
>>>>>> 2013-10-10 15:01:47.761:INFO::NO JSP Support for /solr, did not find
>>>>>> org.apache.jasper.servlet.**JspServlet
>>>>>> 2013-10-10 15:01:47.868:WARN::failed SolrRequestFilter:
>>>>>> org.apache.solr.common.**SolrException: Could not find necessary SLF4j
>>>>>> logging jars. If using Jetty, the SLF4j logging jars need to go in the
>>>>>> jetty lib/ext directory. For other containers, the corresponding
>>>>>> directory
>>>>>> should be used. For more information, see:
>>>>>> http://wiki.apache.org/solr/**SolrLogging<http://wiki.apache.org/solr/SolrLogging>
>>>>>> 2013-10-10 15:01:47.869:WARN::Failed startup of context
>>>>>> org.mortbay.jetty.webapp.**WebAppContext@a13f991
>>>>>> {/solr,file:/var/lib/jetty/**webapps/solr.war}
>>>>>> org.apache.solr.common.**SolrException: Could not find necessary SLF4j
>>>>>> logging jars. If using Jetty, the SLF4j logging jars need to go in the
>>>>>> jetty lib/ext directory. For other containers, the corresponding
>>>>>> directory
>>>>>> should be used. For more information, see:
>>>>>> http://wiki.apache.org/solr/**SolrLogging<http://wiki.apache.org/solr/SolrLogging>
>>>>>> at
>>>>>> org.apache.solr.servlet.**SolrDispatchFilter.<init>(**
>>>>>> SolrDispatchFilter.java:104)
>>>>>> at sun.reflect.**NativeConstructorAccessorImpl.**
>>>>>> newInstance0(Native
>>>>>> Method)
>>>>>> at
>>>>>> sun.reflect.**NativeConstructorAccessorImpl.**newInstance(**
>>>>>> NativeConstructorAccessorImpl.**java:57)
>>>>>> at
>>>>>> sun.reflect.**DelegatingConstructorAccessorI**mpl.newInstance(**
>>>>>> DelegatingConstructorAccessorI**mpl.java:45)
>>>>>> at java.lang.reflect.Constructor.**
>>>>>> newInstance(Constructor.java:**532)
>>>>>> at java.lang.Class.newInstance0(**Class.java:374)
>>>>>> at java.lang.Class.newInstance(**Class.java:327)
>>>>>> at org.mortbay.jetty.servlet.**Holder.newInstance(Holder.**
>>>>>> java:153)
>>>>>> at
>>>>>> org.mortbay.jetty.servlet.**FilterHolder.doStart(**
>>>>>> FilterHolder.java:92)
>>>>>> at
>>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>>> AbstractLifeCycle.java:50)
>>>>>> at
>>>>>> org.mortbay.jetty.servlet.**ServletHandler.initialize(**
>>>>>> ServletHandler.java:662)
>>>>>> at org.mortbay.jetty.servlet.**Context.startContext(Context.*
>>>>>> *java:140)
>>>>>> at
>>>>>> org.mortbay.jetty.webapp.**WebAppContext.startContext(**
>>>>>> WebAppContext.java:1250)
>>>>>> at
>>>>>> org.mortbay.jetty.handler.**ContextHandler.doStart(**
>>>>>> ContextHandler.java:518)
>>>>>> at
>>>>>> org.mortbay.jetty.webapp.**WebAppContext.doStart(**
>>>>>> WebAppContext.java:467)
>>>>>> at
>>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>>> AbstractLifeCycle.java:50)
>>>>>> at
>>>>>> org.mortbay.jetty.handler.**HandlerCollection.doStart(**
>>>>>> HandlerCollection.java:152)
>>>>>> at
>>>>>> org.mortbay.jetty.handler.**ContextHandlerCollection.**doStart(**
>>>>>> ContextHandlerCollection.java:**156)
>>>>>> at
>>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>>> AbstractLifeCycle.java:50)
>>>>>> at
>>>>>> org.mortbay.jetty.handler.**HandlerCollection.doStart(**
>>>>>> HandlerCollection.java:152)
>>>>>> at
>>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>>> AbstractLifeCycle.java:50)
>>>>>> at
>>>>>> org.mortbay.jetty.handler.**HandlerWrapper.doStart(**
>>>>>> HandlerWrapper.java:130)
>>>>>> at org.mortbay.jetty.Server.**doStart(Server.java:224)
>>>>>> at
>>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>>> AbstractLifeCycle.java:50)
>>>>>> at org.mortbay.xml.**XmlConfiguration.main(**
>>>>>> XmlConfiguration.java:985)
>>>>>> at sun.reflect.**NativeMethodAccessorImpl.**invoke0(Native
>>>>>> Method)
>>>>>> at
>>>>>> sun.reflect.**NativeMethodAccessorImpl.**invoke(**
>>>>>> NativeMethodAccessorImpl.java:**57)
>>>>>> at
>>>>>> sun.reflect.**DelegatingMethodAccessorImpl.**invoke(**
>>>>>> DelegatingMethodAccessorImpl.**java:43)
>>>>>> at java.lang.reflect.Method.**invoke(Method.java:616)
>>>>>> at org.mortbay.start.Main.**invokeMain(Main.java:194)
>>>>>> at org.mortbay.start.Main.start(**Main.java:534)
>>>>>> at org.mortbay.start.Main.start(**Main.java:441)
>>>>>> at org.mortbay.start.Main.main(**Main.java:119)
>>>>>> 2013-10-10 15:01:47.870:WARN::failed
>>>>>> org.mortbay.jetty.webapp.**WebAppContext@a13f991{/solr,**
>>>>>> file:/var/lib/jetty/webapps/**solr.war}:
>>>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>>>> 2013-10-10 15:01:47.870:WARN::failed ContextHandlerCollection@**
>>>>>> 2565a3c2:
>>>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>>>> 2013-10-10 15:01:47.870:INFO::Opened /var/log/jetty/2013_10_10.**
>>>>>> request.log
>>>>>> 2013-10-10 15:01:47.871:WARN::failed HandlerCollection@33e228bc:
>>>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>>>> 2013-10-10 15:01:47.871:WARN::Error starting handlers
>>>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>>>> at java.lang.Class.**getDeclaredMethods0(Native Method)
>>>>>> at java.lang.Class.**privateGetDeclaredMethods(**
>>>>>> Class.java:2482)
>>>>>> at java.lang.Class.getMethod0(**Class.java:2725)
>>>>>> at java.lang.Class.getMethod(**Class.java:1650)
>>>>>> at org.mortbay.log.Log.unwind(**Log.java:228)
>>>>>> at org.mortbay.log.Log.warn(Log.**java:197)
>>>>>> at
>>>>>> org.mortbay.jetty.webapp.**WebAppContext.doStart(**
>>>>>> WebAppContext.java:475)
>>>>>> ...
>>>>>>
>>>>>> And when i copy the jars from solr-4.4.0/example/lib and
>>>>>> solr-4.4.0/example/lib and solr-4.4.0/example/lib/ext to jettys lib
>>>>>> directory and lib/ext the server is not starting anymore. Quits with
>>>>>> JETTY:
>>>>>> Failed without logging something
>>>>>>
>>>>>>
>>>>>>
>>>>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>>>>
>>>>>> Check the jetty logs, there must be something wrong in your collection
>>>>>>> config, usually if it doesn't start it will tell you there.
>>>>>>>
>>>>>>> And of course, for every change you make be sure you restart jetty.
>>>>>>>
>>>>>>> Guido.
>>>>>>>
>>>>>>>
>>>>>>> On 10/10/13 13:20, Peter Schmidt wrote:
>>>>>>>
>>>>>>> No, it's not working that easy with the jetty 6.1.
>>>>>>>> When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
>>>>>>>> solr.war in the jetty webapps directory i got a 404 when in try to
>>>>>>>> reach
>>>>>>>> http://localhost:8080 or http://localhost:8080/solr.
>>>>>>>>
>>>>>>>>
>>>>>>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>>>>>>
>>>>>>>> My I forgot to mention where you need to copy the solr.war file:
>>>>>>>>
>>>>>>>>> /var/lib/jetty/webapps
>>>>>>>>>
>>>>>>>>> Guido.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 10/10/13 10:48, Guido Medina wrote:
>>>>>>>>>
>>>>>>>>> Here is the pertinent changes you need to pass to
>>>>>>>>> /etc/default/jetty:
>>>>>>>>>
>>>>>>>>>> * JAVA_OPTIONS="-Djava.awt.******headless=true
>>>>>>>>>> -Dfile.encoding=UTF-8
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>>>>>>>>>> * JAVA_OPTIONS="-Dsolr.solr.******
>>>>>>>>>> home=$YOUR_SOLR_COLLECTION_******HOME
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> $JAVA_OPTIONS"
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to
>>>>>>>>>> play
>>>>>>>>>> with it. Adjust your solr collection home to whatever path is on
>>>>>>>>>> your
>>>>>>>>>> system.
>>>>>>>>>>
>>>>>>>>>> HTH,
>>>>>>>>>>
>>>>>>>>>> Guido.
>>>>>>>>>>
>>>>>>>>>> On 10/10/13 10:43, Guido Medina wrote:
>>>>>>>>>>
>>>>>>>>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from
>>>>>>>>>> Ubuntu
>>>>>>>>>>
>>>>>>>>>>> repo, we have in production for few years now with no issues, you
>>>>>>>>>>> just need
>>>>>>>>>>> to be sure your solr.war has the required jars in it, also your
>>>>>>>>>>> collection
>>>>>>>>>>> must have the extra jars needed by your app.
>>>>>>>>>>>
>>>>>>>>>>> We have been running it in Ubuntu Server 12.04 LTS for a long
>>>>>>>>>>> time, it
>>>>>>>>>>> is easy to have the jetty server with default repo package since
>>>>>>>>>>> it
>>>>>>>>>>> is easy
>>>>>>>>>>> to pass JVM parameters using /etc/default/jetty config file.
>>>>>>>>>>>
>>>>>>>>>>> HTH,
>>>>>>>>>>>
>>>>>>>>>>> Guido.
>>>>>>>>>>>
>>>>>>>>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>>>>>>>>>
>>>>>>>>>>> Do you get an error?
>>>>>>>>>>>
>>>>>>>>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>>>>
>>>>>>>>>>>> Hey folks,
>>>>>>>>>>>>
>>>>>>>>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with
>>>>>>>>>>>>> Jetty
>>>>>>>>>>>>> 6.1
>>>>>>>>>>>>> from the Ubuntu repository installed with apt-get. First i
>>>>>>>>>>>>> tried the
>>>>>>>>>>>>> installation according the wiki http://wiki.apache.org/solr/**
>>>>>>>>>>>>> SolrJetty <http://wiki.apache.org/solr/****SolrJetty<http://wiki.apache.org/solr/**SolrJetty>
>>>>>>>>>>>>> <http://wiki.apache.**org/solr/SolrJetty<http://wiki.apache.org/solr/SolrJetty>
>>>>>>>>>>>>> .
>>>>>>>>>>>>> Then
>>>>>>>>>>>>> i found this example
>>>>>>>>>>>>> http://www.kingstonlabs.com/******blog/how-to-install-solr-36-*
>>>>>>>>>>>>> ***<http://www.kingstonlabs.com/****blog/how-to-install-solr-36-**>
>>>>>>>>>>>>> <http://www.kingstonlabs.**com/**blog/how-to-install-**
>>>>>>>>>>>>> solr-36-**<http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**>
>>>>>>>>>>>>> on-ubuntu-1204/and<http://www.****kingstonlabs.com/blog/how-**
>>>>>>>>>>>>> to-** <http://kingstonlabs.com/blog/how-to-**>
>>>>>>>>>>>>> install-solr-36-on-ubuntu-****1204/and<http://www.**
>>>>>>>>>>>>> kingstonlabs.com/blog/how-to-**install-solr-36-on-ubuntu-**
>>>>>>>>>>>>> 1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>>>>>>>>>> tried the Configuration according to the book pache Solr 4
>>>>>>>>>>>>> Cookbook
>>>>>>>>>>>>> by
>>>>>>>>>>>>> Rafal Kuc.
>>>>>>>>>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on
>>>>>>>>>>>>> Ubuntus
>>>>>>>>>>>>> jetty 6.1 :(
>>>>>>>>>>>>> Can somebody confirm that it's impossible or give me an advice
>>>>>>>>>>>>> how
>>>>>>>>>>>>> to
>>>>>>>>>>>>> run
>>>>>>>>>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>>>>>>>>>> Regards
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
SOLVED: I reinstalled the jetty package, because i wanted to get a clean
installation. And now it's working with your hint Guido :-) Thank you very
much.
What i did:
# Download Solr
wget http://archive.apache.org/dist/lucene/solr/4.4.0/solr-4.4.0.tgz
tar xvfz solr-4.4.0.tgz
# Extract content from solr.war and add missing jars from the lib/ext like
Guido described
mkdir dir_to_extract
cp -R solr-4.4.0/example/webapps/solr.war dir_to_extract
cd dir_to_extract
unzip solr.war
rm solr.war
cp ../solr-4.4.0/example/lib/ext/*.jar WEB-INF/lib/
jar -cvf solr.war *
# copy new var to jetty webapps folder
sudo cp solr.war /usr/share/jetty/webapps
# Copy Solr example files
sudo mkdir /usr/share/solr
sudo cp -R solr-4.4.0/example/* /usr/share/solr/
sudo chmod -R jetty:adm /usr/share/solr
# Edit jetty config
vi /etc/default/jetty
NO_START=0
VERBOSE=yes
JETTY_HOST=0.0.0.0
JAVA_OPTIONS="-Xmx256m -Djava.awt.headless=true
-Dsolr.solr.home=/usr/share/solr/solr $JAVA_OPTIONS"
And then Solr 4.4.0 is accessible on http://localhost:8080/solr
But i also saw the box with the hint on
https://cwiki.apache.org/confluence/display/solr/Installing+Solr:
"Solr ships with a working Jetty server, with optimized settings for Solr,
inside the example directory. It is recommended that you use the provided
Jetty server for optimal performance. If you absolutely must use a
different servlet container then continue to the next section on how to
install Solr."
@Guido: Do you know if the performance is weaker with the Jetty 6.1?
And which Jetty version is the inluded one?
2013/10/10 Peter Schmidt <pe...@gmail.com>
> i added the jars you have listet and recreated a solr.war
>
>
> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>
>> OK. I extracted the solr.war in webapps folder. And than out.log reports
>>
>> 2013-10-10 16:47:28.184:WARN::Config error at <New id="ServerLog"
>> class="java.io.PrintStream"><Arg>| <New
>> class="org.mortbay.util.RolloverFileOutputStream"><Arg><SystemProperty
>> name="jetty.home" default="."/>/logs/yyyy_mm_dd.stderrout.log</Arg><Arg
>> type="boolean">false</Arg><Arg type="int">90</Arg><Arg><Call
>> class="java.util.TimeZone"
>> name="getTimeZone"><Arg>GMT</Arg></Call></Arg><Get id="ServerLogName"
>> name="datedFilename"/></New>| </Arg></New>
>> java.lang.reflect.InvocationTargetException
>> 2013-10-10 16:47:28.191:WARN::EXCEPTION
>> java.lang.reflect.InvocationTargetException
>>
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> Method)
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>> at
>> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:608)
>> at
>> org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:915)
>> at
>> org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:837)
>> at
>> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:593)
>> at
>> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:256)
>> at
>> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
>> at
>> org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:616)
>> at org.mortbay.start.Main.invokeMain(Main.java:194)
>> at org.mortbay.start.Main.start(Main.java:534)
>> at
>> org.mortbay.jetty.start.daemon.Bootstrap.start(Bootstrap.java:30)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:616)
>> at
>> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
>> 2013-10-10 16:47:28.192:WARN::Nested in
>> java.lang.reflect.InvocationTargetException:
>> java.io.IOException: Cannot write log file
>> /var/log/jetty/2013_10_10.stderrout.log
>> at
>> org.mortbay.util.RolloverFileOutputStream.setFile(RolloverFileOutputStream.java:233)
>> at
>> org.mortbay.util.RolloverFileOutputStream.<init>(RolloverFileOutputStream.java:164)
>> at
>> org.mortbay.util.RolloverFileOutputStream.<init>(RolloverFileOutputStream.java:116)
>>
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> Method)
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>> at
>> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:608)
>> at
>> org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:915)
>> at
>> org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:837)
>> at
>> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:593)
>> at
>> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:256)
>> at
>> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
>> at
>> org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:616)
>> at org.mortbay.start.Main.invokeMain(Main.java:194)
>> at org.mortbay.start.Main.start(Main.java:534)
>> at
>> org.mortbay.jetty.start.daemon.Bootstrap.start(Bootstrap.java:30)
>>
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:616)
>> at
>> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
>>
>>
>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>
>>> Add the following jars inside solr.war WEB-INF/lib folder:
>>>
>>> jcl-over-slf4j-1.7.5.jar
>>> jul-to-slf4j-1.7.5.jar
>>> log4j-1.2.17.jar
>>> slf4j-api-1.7.5.jar
>>> slf4j-log4j12-1.7.5.jar
>>>
>>> Optional if you are going to use spatial search:
>>> jts-1.13.jar
>>>
>>> Guido.
>>>
>>>
>>> On 10/10/13 14:33, Peter Schmidt wrote:
>>>
>>>> Sorry terminal shows:
>>>>
>>>> $ sudo service jetty start
>>>> Found JAVA=/usr/lib/jvm/java-6-**openjdk/jre/bin/java in JAVA_HOME=/
>>>> Starting Jetty: FAILED
>>>>
>>>>
>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>
>>>> The log:
>>>>>
>>>>> 2013-10-10 15:01:47.071:INFO::jetty-6.1.**22
>>>>> 2013-10-10 15:01:47.110:INFO::Deploy /etc/jetty/contexts/javadoc.**xml
>>>>> ->
>>>>> org.mortbay.jetty.handler.**ContextHandler@2353f67e
>>>>> {/javadoc,file:/usr/share/doc/**libjetty-java/api/}
>>>>> 2013-10-10 15:01:47.161:INFO::NO JSP Support for , did not find
>>>>> org.apache.jasper.servlet.**JspServlet
>>>>> 2013-10-10 15:01:47.192:INFO::Extract file:/var/lib/jetty/webapps/**
>>>>> solr.war
>>>>> to /tmp/Jetty_0_0_0_0_8080_solr.**war__solr__7k9npr/webapp
>>>>> 2013-10-10 15:01:47.761:INFO::NO JSP Support for /solr, did not find
>>>>> org.apache.jasper.servlet.**JspServlet
>>>>> 2013-10-10 15:01:47.868:WARN::failed SolrRequestFilter:
>>>>> org.apache.solr.common.**SolrException: Could not find necessary SLF4j
>>>>> logging jars. If using Jetty, the SLF4j logging jars need to go in the
>>>>> jetty lib/ext directory. For other containers, the corresponding
>>>>> directory
>>>>> should be used. For more information, see:
>>>>> http://wiki.apache.org/solr/**SolrLogging<http://wiki.apache.org/solr/SolrLogging>
>>>>> 2013-10-10 15:01:47.869:WARN::Failed startup of context
>>>>> org.mortbay.jetty.webapp.**WebAppContext@a13f991
>>>>> {/solr,file:/var/lib/jetty/**webapps/solr.war}
>>>>> org.apache.solr.common.**SolrException: Could not find necessary SLF4j
>>>>> logging jars. If using Jetty, the SLF4j logging jars need to go in the
>>>>> jetty lib/ext directory. For other containers, the corresponding
>>>>> directory
>>>>> should be used. For more information, see:
>>>>> http://wiki.apache.org/solr/**SolrLogging<http://wiki.apache.org/solr/SolrLogging>
>>>>> at
>>>>> org.apache.solr.servlet.**SolrDispatchFilter.<init>(**
>>>>> SolrDispatchFilter.java:104)
>>>>> at sun.reflect.**NativeConstructorAccessorImpl.**
>>>>> newInstance0(Native
>>>>> Method)
>>>>> at
>>>>> sun.reflect.**NativeConstructorAccessorImpl.**newInstance(**
>>>>> NativeConstructorAccessorImpl.**java:57)
>>>>> at
>>>>> sun.reflect.**DelegatingConstructorAccessorI**mpl.newInstance(**
>>>>> DelegatingConstructorAccessorI**mpl.java:45)
>>>>> at java.lang.reflect.Constructor.**
>>>>> newInstance(Constructor.java:**532)
>>>>> at java.lang.Class.newInstance0(**Class.java:374)
>>>>> at java.lang.Class.newInstance(**Class.java:327)
>>>>> at org.mortbay.jetty.servlet.**Holder.newInstance(Holder.**
>>>>> java:153)
>>>>> at
>>>>> org.mortbay.jetty.servlet.**FilterHolder.doStart(**
>>>>> FilterHolder.java:92)
>>>>> at
>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>> AbstractLifeCycle.java:50)
>>>>> at
>>>>> org.mortbay.jetty.servlet.**ServletHandler.initialize(**
>>>>> ServletHandler.java:662)
>>>>> at org.mortbay.jetty.servlet.**Context.startContext(Context.*
>>>>> *java:140)
>>>>> at
>>>>> org.mortbay.jetty.webapp.**WebAppContext.startContext(**
>>>>> WebAppContext.java:1250)
>>>>> at
>>>>> org.mortbay.jetty.handler.**ContextHandler.doStart(**
>>>>> ContextHandler.java:518)
>>>>> at
>>>>> org.mortbay.jetty.webapp.**WebAppContext.doStart(**
>>>>> WebAppContext.java:467)
>>>>> at
>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>> AbstractLifeCycle.java:50)
>>>>> at
>>>>> org.mortbay.jetty.handler.**HandlerCollection.doStart(**
>>>>> HandlerCollection.java:152)
>>>>> at
>>>>> org.mortbay.jetty.handler.**ContextHandlerCollection.**doStart(**
>>>>> ContextHandlerCollection.java:**156)
>>>>> at
>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>> AbstractLifeCycle.java:50)
>>>>> at
>>>>> org.mortbay.jetty.handler.**HandlerCollection.doStart(**
>>>>> HandlerCollection.java:152)
>>>>> at
>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>> AbstractLifeCycle.java:50)
>>>>> at
>>>>> org.mortbay.jetty.handler.**HandlerWrapper.doStart(**
>>>>> HandlerWrapper.java:130)
>>>>> at org.mortbay.jetty.Server.**doStart(Server.java:224)
>>>>> at
>>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>>> AbstractLifeCycle.java:50)
>>>>> at org.mortbay.xml.**XmlConfiguration.main(**
>>>>> XmlConfiguration.java:985)
>>>>> at sun.reflect.**NativeMethodAccessorImpl.**invoke0(Native
>>>>> Method)
>>>>> at
>>>>> sun.reflect.**NativeMethodAccessorImpl.**invoke(**
>>>>> NativeMethodAccessorImpl.java:**57)
>>>>> at
>>>>> sun.reflect.**DelegatingMethodAccessorImpl.**invoke(**
>>>>> DelegatingMethodAccessorImpl.**java:43)
>>>>> at java.lang.reflect.Method.**invoke(Method.java:616)
>>>>> at org.mortbay.start.Main.**invokeMain(Main.java:194)
>>>>> at org.mortbay.start.Main.start(**Main.java:534)
>>>>> at org.mortbay.start.Main.start(**Main.java:441)
>>>>> at org.mortbay.start.Main.main(**Main.java:119)
>>>>> 2013-10-10 15:01:47.870:WARN::failed
>>>>> org.mortbay.jetty.webapp.**WebAppContext@a13f991{/solr,**
>>>>> file:/var/lib/jetty/webapps/**solr.war}:
>>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>>> 2013-10-10 15:01:47.870:WARN::failed ContextHandlerCollection@**
>>>>> 2565a3c2:
>>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>>> 2013-10-10 15:01:47.870:INFO::Opened /var/log/jetty/2013_10_10.**
>>>>> request.log
>>>>> 2013-10-10 15:01:47.871:WARN::failed HandlerCollection@33e228bc:
>>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>>> 2013-10-10 15:01:47.871:WARN::Error starting handlers
>>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>>> at java.lang.Class.**getDeclaredMethods0(Native Method)
>>>>> at java.lang.Class.**privateGetDeclaredMethods(**
>>>>> Class.java:2482)
>>>>> at java.lang.Class.getMethod0(**Class.java:2725)
>>>>> at java.lang.Class.getMethod(**Class.java:1650)
>>>>> at org.mortbay.log.Log.unwind(**Log.java:228)
>>>>> at org.mortbay.log.Log.warn(Log.**java:197)
>>>>> at
>>>>> org.mortbay.jetty.webapp.**WebAppContext.doStart(**
>>>>> WebAppContext.java:475)
>>>>> ...
>>>>>
>>>>> And when i copy the jars from solr-4.4.0/example/lib and
>>>>> solr-4.4.0/example/lib and solr-4.4.0/example/lib/ext to jettys lib
>>>>> directory and lib/ext the server is not starting anymore. Quits with
>>>>> JETTY:
>>>>> Failed without logging something
>>>>>
>>>>>
>>>>>
>>>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>>>
>>>>> Check the jetty logs, there must be something wrong in your collection
>>>>>> config, usually if it doesn't start it will tell you there.
>>>>>>
>>>>>> And of course, for every change you make be sure you restart jetty.
>>>>>>
>>>>>> Guido.
>>>>>>
>>>>>>
>>>>>> On 10/10/13 13:20, Peter Schmidt wrote:
>>>>>>
>>>>>> No, it's not working that easy with the jetty 6.1.
>>>>>>>
>>>>>>> When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
>>>>>>> solr.war in the jetty webapps directory i got a 404 when in try to
>>>>>>> reach
>>>>>>> http://localhost:8080 or http://localhost:8080/solr.
>>>>>>>
>>>>>>>
>>>>>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>>>>>
>>>>>>> My I forgot to mention where you need to copy the solr.war file:
>>>>>>>
>>>>>>>> /var/lib/jetty/webapps
>>>>>>>>
>>>>>>>> Guido.
>>>>>>>>
>>>>>>>>
>>>>>>>> On 10/10/13 10:48, Guido Medina wrote:
>>>>>>>>
>>>>>>>> Here is the pertinent changes you need to pass to
>>>>>>>> /etc/default/jetty:
>>>>>>>>
>>>>>>>>> * JAVA_OPTIONS="-Djava.awt.******headless=true
>>>>>>>>> -Dfile.encoding=UTF-8
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>>>>>>>>> * JAVA_OPTIONS="-Dsolr.solr.******
>>>>>>>>> home=$YOUR_SOLR_COLLECTION_******HOME
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> $JAVA_OPTIONS"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to
>>>>>>>>> play
>>>>>>>>> with it. Adjust your solr collection home to whatever path is on
>>>>>>>>> your
>>>>>>>>> system.
>>>>>>>>>
>>>>>>>>> HTH,
>>>>>>>>>
>>>>>>>>> Guido.
>>>>>>>>>
>>>>>>>>> On 10/10/13 10:43, Guido Medina wrote:
>>>>>>>>>
>>>>>>>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from
>>>>>>>>> Ubuntu
>>>>>>>>>
>>>>>>>>>> repo, we have in production for few years now with no issues, you
>>>>>>>>>> just need
>>>>>>>>>> to be sure your solr.war has the required jars in it, also your
>>>>>>>>>> collection
>>>>>>>>>> must have the extra jars needed by your app.
>>>>>>>>>>
>>>>>>>>>> We have been running it in Ubuntu Server 12.04 LTS for a long
>>>>>>>>>> time, it
>>>>>>>>>> is easy to have the jetty server with default repo package since
>>>>>>>>>> it
>>>>>>>>>> is easy
>>>>>>>>>> to pass JVM parameters using /etc/default/jetty config file.
>>>>>>>>>>
>>>>>>>>>> HTH,
>>>>>>>>>>
>>>>>>>>>> Guido.
>>>>>>>>>>
>>>>>>>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>>>>>>>>
>>>>>>>>>> Do you get an error?
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>>>
>>>>>>>>>>> Hey folks,
>>>>>>>>>>>
>>>>>>>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with
>>>>>>>>>>>> Jetty
>>>>>>>>>>>> 6.1
>>>>>>>>>>>> from the Ubuntu repository installed with apt-get. First i
>>>>>>>>>>>> tried the
>>>>>>>>>>>> installation according the wiki http://wiki.apache.org/solr/**
>>>>>>>>>>>> SolrJetty <http://wiki.apache.org/solr/****SolrJetty<http://wiki.apache.org/solr/**SolrJetty>
>>>>>>>>>>>> <http://wiki.apache.**org/solr/SolrJetty<http://wiki.apache.org/solr/SolrJetty>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>> .
>>>>>>>>>>>>>
>>>>>>>>>>>> Then
>>>>>>>>>>>> i found this example
>>>>>>>>>>>> http://www.kingstonlabs.com/******blog/how-to-install-solr-36-*
>>>>>>>>>>>> ***<http://www.kingstonlabs.com/****blog/how-to-install-solr-36-**>
>>>>>>>>>>>> <http://www.kingstonlabs.**com/**blog/how-to-install-**
>>>>>>>>>>>> solr-36-**<http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**>
>>>>>>>>>>>> >
>>>>>>>>>>>> on-ubuntu-1204/and<http://www.****kingstonlabs.com/blog/how-**
>>>>>>>>>>>> to-** <http://kingstonlabs.com/blog/how-to-**>
>>>>>>>>>>>> install-solr-36-on-ubuntu-****1204/and<http://www.**
>>>>>>>>>>>> kingstonlabs.com/blog/how-to-**install-solr-36-on-ubuntu-**
>>>>>>>>>>>> 1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>>>>>>>>> >
>>>>>>>>>>>>
>>>>>>>>>>>> tried the Configuration according to the book pache Solr 4
>>>>>>>>>>>> Cookbook
>>>>>>>>>>>> by
>>>>>>>>>>>> Rafal Kuc.
>>>>>>>>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on
>>>>>>>>>>>> Ubuntus
>>>>>>>>>>>> jetty 6.1 :(
>>>>>>>>>>>> Can somebody confirm that it's impossible or give me an advice
>>>>>>>>>>>> how
>>>>>>>>>>>> to
>>>>>>>>>>>> run
>>>>>>>>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>>>>>>>>> Regards
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>
>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
i added the jars you have listet and recreated a solr.war
2013/10/10 Peter Schmidt <pe...@gmail.com>
> OK. I extracted the solr.war in webapps folder. And than out.log reports
>
> 2013-10-10 16:47:28.184:WARN::Config error at <New id="ServerLog"
> class="java.io.PrintStream"><Arg>| <New
> class="org.mortbay.util.RolloverFileOutputStream"><Arg><SystemProperty
> name="jetty.home" default="."/>/logs/yyyy_mm_dd.stderrout.log</Arg><Arg
> type="boolean">false</Arg><Arg type="int">90</Arg><Arg><Call
> class="java.util.TimeZone"
> name="getTimeZone"><Arg>GMT</Arg></Call></Arg><Get id="ServerLogName"
> name="datedFilename"/></New>| </Arg></New>
> java.lang.reflect.InvocationTargetException
> 2013-10-10 16:47:28.191:WARN::EXCEPTION
> java.lang.reflect.InvocationTargetException
>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> at
> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:608)
> at
> org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:915)
> at
> org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:837)
> at
> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:593)
> at
> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:256)
> at
> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
> at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.mortbay.start.Main.invokeMain(Main.java:194)
> at org.mortbay.start.Main.start(Main.java:534)
> at
> org.mortbay.jetty.start.daemon.Bootstrap.start(Bootstrap.java:30)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
> 2013-10-10 16:47:28.192:WARN::Nested in
> java.lang.reflect.InvocationTargetException:
> java.io.IOException: Cannot write log file
> /var/log/jetty/2013_10_10.stderrout.log
> at
> org.mortbay.util.RolloverFileOutputStream.setFile(RolloverFileOutputStream.java:233)
> at
> org.mortbay.util.RolloverFileOutputStream.<init>(RolloverFileOutputStream.java:164)
> at
> org.mortbay.util.RolloverFileOutputStream.<init>(RolloverFileOutputStream.java:116)
>
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> at
> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:608)
> at
> org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:915)
> at
> org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:837)
> at
> org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:593)
> at
> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:256)
> at
> org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
> at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.mortbay.start.Main.invokeMain(Main.java:194)
> at org.mortbay.start.Main.start(Main.java:534)
> at
> org.mortbay.jetty.start.daemon.Bootstrap.start(Bootstrap.java:30)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
>
>
> 2013/10/10 Guido Medina <gu...@temetra.com>
>
>> Add the following jars inside solr.war WEB-INF/lib folder:
>>
>> jcl-over-slf4j-1.7.5.jar
>> jul-to-slf4j-1.7.5.jar
>> log4j-1.2.17.jar
>> slf4j-api-1.7.5.jar
>> slf4j-log4j12-1.7.5.jar
>>
>> Optional if you are going to use spatial search:
>> jts-1.13.jar
>>
>> Guido.
>>
>>
>> On 10/10/13 14:33, Peter Schmidt wrote:
>>
>>> Sorry terminal shows:
>>>
>>> $ sudo service jetty start
>>> Found JAVA=/usr/lib/jvm/java-6-**openjdk/jre/bin/java in JAVA_HOME=/
>>> Starting Jetty: FAILED
>>>
>>>
>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>
>>> The log:
>>>>
>>>> 2013-10-10 15:01:47.071:INFO::jetty-6.1.**22
>>>> 2013-10-10 15:01:47.110:INFO::Deploy /etc/jetty/contexts/javadoc.**xml
>>>> ->
>>>> org.mortbay.jetty.handler.**ContextHandler@2353f67e
>>>> {/javadoc,file:/usr/share/doc/**libjetty-java/api/}
>>>> 2013-10-10 15:01:47.161:INFO::NO JSP Support for , did not find
>>>> org.apache.jasper.servlet.**JspServlet
>>>> 2013-10-10 15:01:47.192:INFO::Extract file:/var/lib/jetty/webapps/**
>>>> solr.war
>>>> to /tmp/Jetty_0_0_0_0_8080_solr.**war__solr__7k9npr/webapp
>>>> 2013-10-10 15:01:47.761:INFO::NO JSP Support for /solr, did not find
>>>> org.apache.jasper.servlet.**JspServlet
>>>> 2013-10-10 15:01:47.868:WARN::failed SolrRequestFilter:
>>>> org.apache.solr.common.**SolrException: Could not find necessary SLF4j
>>>> logging jars. If using Jetty, the SLF4j logging jars need to go in the
>>>> jetty lib/ext directory. For other containers, the corresponding
>>>> directory
>>>> should be used. For more information, see:
>>>> http://wiki.apache.org/solr/**SolrLogging<http://wiki.apache.org/solr/SolrLogging>
>>>> 2013-10-10 15:01:47.869:WARN::Failed startup of context
>>>> org.mortbay.jetty.webapp.**WebAppContext@a13f991
>>>> {/solr,file:/var/lib/jetty/**webapps/solr.war}
>>>> org.apache.solr.common.**SolrException: Could not find necessary SLF4j
>>>> logging jars. If using Jetty, the SLF4j logging jars need to go in the
>>>> jetty lib/ext directory. For other containers, the corresponding
>>>> directory
>>>> should be used. For more information, see:
>>>> http://wiki.apache.org/solr/**SolrLogging<http://wiki.apache.org/solr/SolrLogging>
>>>> at
>>>> org.apache.solr.servlet.**SolrDispatchFilter.<init>(**
>>>> SolrDispatchFilter.java:104)
>>>> at sun.reflect.**NativeConstructorAccessorImpl.**
>>>> newInstance0(Native
>>>> Method)
>>>> at
>>>> sun.reflect.**NativeConstructorAccessorImpl.**newInstance(**
>>>> NativeConstructorAccessorImpl.**java:57)
>>>> at
>>>> sun.reflect.**DelegatingConstructorAccessorI**mpl.newInstance(**
>>>> DelegatingConstructorAccessorI**mpl.java:45)
>>>> at java.lang.reflect.Constructor.**
>>>> newInstance(Constructor.java:**532)
>>>> at java.lang.Class.newInstance0(**Class.java:374)
>>>> at java.lang.Class.newInstance(**Class.java:327)
>>>> at org.mortbay.jetty.servlet.**Holder.newInstance(Holder.**
>>>> java:153)
>>>> at
>>>> org.mortbay.jetty.servlet.**FilterHolder.doStart(**
>>>> FilterHolder.java:92)
>>>> at
>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>> AbstractLifeCycle.java:50)
>>>> at
>>>> org.mortbay.jetty.servlet.**ServletHandler.initialize(**
>>>> ServletHandler.java:662)
>>>> at org.mortbay.jetty.servlet.**Context.startContext(Context.**
>>>> java:140)
>>>> at
>>>> org.mortbay.jetty.webapp.**WebAppContext.startContext(**
>>>> WebAppContext.java:1250)
>>>> at
>>>> org.mortbay.jetty.handler.**ContextHandler.doStart(**
>>>> ContextHandler.java:518)
>>>> at
>>>> org.mortbay.jetty.webapp.**WebAppContext.doStart(**
>>>> WebAppContext.java:467)
>>>> at
>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>> AbstractLifeCycle.java:50)
>>>> at
>>>> org.mortbay.jetty.handler.**HandlerCollection.doStart(**
>>>> HandlerCollection.java:152)
>>>> at
>>>> org.mortbay.jetty.handler.**ContextHandlerCollection.**doStart(**
>>>> ContextHandlerCollection.java:**156)
>>>> at
>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>> AbstractLifeCycle.java:50)
>>>> at
>>>> org.mortbay.jetty.handler.**HandlerCollection.doStart(**
>>>> HandlerCollection.java:152)
>>>> at
>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>> AbstractLifeCycle.java:50)
>>>> at
>>>> org.mortbay.jetty.handler.**HandlerWrapper.doStart(**
>>>> HandlerWrapper.java:130)
>>>> at org.mortbay.jetty.Server.**doStart(Server.java:224)
>>>> at
>>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>>> AbstractLifeCycle.java:50)
>>>> at org.mortbay.xml.**XmlConfiguration.main(**
>>>> XmlConfiguration.java:985)
>>>> at sun.reflect.**NativeMethodAccessorImpl.**invoke0(Native
>>>> Method)
>>>> at
>>>> sun.reflect.**NativeMethodAccessorImpl.**invoke(**
>>>> NativeMethodAccessorImpl.java:**57)
>>>> at
>>>> sun.reflect.**DelegatingMethodAccessorImpl.**invoke(**
>>>> DelegatingMethodAccessorImpl.**java:43)
>>>> at java.lang.reflect.Method.**invoke(Method.java:616)
>>>> at org.mortbay.start.Main.**invokeMain(Main.java:194)
>>>> at org.mortbay.start.Main.start(**Main.java:534)
>>>> at org.mortbay.start.Main.start(**Main.java:441)
>>>> at org.mortbay.start.Main.main(**Main.java:119)
>>>> 2013-10-10 15:01:47.870:WARN::failed
>>>> org.mortbay.jetty.webapp.**WebAppContext@a13f991{/solr,**
>>>> file:/var/lib/jetty/webapps/**solr.war}:
>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>> 2013-10-10 15:01:47.870:WARN::failed ContextHandlerCollection@**
>>>> 2565a3c2:
>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>> 2013-10-10 15:01:47.870:INFO::Opened /var/log/jetty/2013_10_10.**
>>>> request.log
>>>> 2013-10-10 15:01:47.871:WARN::failed HandlerCollection@33e228bc:
>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>> 2013-10-10 15:01:47.871:WARN::Error starting handlers
>>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>>> at java.lang.Class.**getDeclaredMethods0(Native Method)
>>>> at java.lang.Class.**privateGetDeclaredMethods(**
>>>> Class.java:2482)
>>>> at java.lang.Class.getMethod0(**Class.java:2725)
>>>> at java.lang.Class.getMethod(**Class.java:1650)
>>>> at org.mortbay.log.Log.unwind(**Log.java:228)
>>>> at org.mortbay.log.Log.warn(Log.**java:197)
>>>> at
>>>> org.mortbay.jetty.webapp.**WebAppContext.doStart(**
>>>> WebAppContext.java:475)
>>>> ...
>>>>
>>>> And when i copy the jars from solr-4.4.0/example/lib and
>>>> solr-4.4.0/example/lib and solr-4.4.0/example/lib/ext to jettys lib
>>>> directory and lib/ext the server is not starting anymore. Quits with
>>>> JETTY:
>>>> Failed without logging something
>>>>
>>>>
>>>>
>>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>>
>>>> Check the jetty logs, there must be something wrong in your collection
>>>>> config, usually if it doesn't start it will tell you there.
>>>>>
>>>>> And of course, for every change you make be sure you restart jetty.
>>>>>
>>>>> Guido.
>>>>>
>>>>>
>>>>> On 10/10/13 13:20, Peter Schmidt wrote:
>>>>>
>>>>> No, it's not working that easy with the jetty 6.1.
>>>>>>
>>>>>> When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
>>>>>> solr.war in the jetty webapps directory i got a 404 when in try to
>>>>>> reach
>>>>>> http://localhost:8080 or http://localhost:8080/solr.
>>>>>>
>>>>>>
>>>>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>>>>
>>>>>> My I forgot to mention where you need to copy the solr.war file:
>>>>>>
>>>>>>> /var/lib/jetty/webapps
>>>>>>>
>>>>>>> Guido.
>>>>>>>
>>>>>>>
>>>>>>> On 10/10/13 10:48, Guido Medina wrote:
>>>>>>>
>>>>>>> Here is the pertinent changes you need to pass to
>>>>>>> /etc/default/jetty:
>>>>>>>
>>>>>>>> * JAVA_OPTIONS="-Djava.awt.******headless=true
>>>>>>>> -Dfile.encoding=UTF-8
>>>>>>>>
>>>>>>>>
>>>>>>>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>>>>>>>> * JAVA_OPTIONS="-Dsolr.solr.******
>>>>>>>> home=$YOUR_SOLR_COLLECTION_******HOME
>>>>>>>>
>>>>>>>>
>>>>>>>> $JAVA_OPTIONS"
>>>>>>>>
>>>>>>>>
>>>>>>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to
>>>>>>>> play
>>>>>>>> with it. Adjust your solr collection home to whatever path is on
>>>>>>>> your
>>>>>>>> system.
>>>>>>>>
>>>>>>>> HTH,
>>>>>>>>
>>>>>>>> Guido.
>>>>>>>>
>>>>>>>> On 10/10/13 10:43, Guido Medina wrote:
>>>>>>>>
>>>>>>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from
>>>>>>>> Ubuntu
>>>>>>>>
>>>>>>>>> repo, we have in production for few years now with no issues, you
>>>>>>>>> just need
>>>>>>>>> to be sure your solr.war has the required jars in it, also your
>>>>>>>>> collection
>>>>>>>>> must have the extra jars needed by your app.
>>>>>>>>>
>>>>>>>>> We have been running it in Ubuntu Server 12.04 LTS for a long
>>>>>>>>> time, it
>>>>>>>>> is easy to have the jetty server with default repo package since it
>>>>>>>>> is easy
>>>>>>>>> to pass JVM parameters using /etc/default/jetty config file.
>>>>>>>>>
>>>>>>>>> HTH,
>>>>>>>>>
>>>>>>>>> Guido.
>>>>>>>>>
>>>>>>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>>>>>>>
>>>>>>>>> Do you get an error?
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>>
>>>>>>>>>> Hey folks,
>>>>>>>>>>
>>>>>>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with
>>>>>>>>>>> Jetty
>>>>>>>>>>> 6.1
>>>>>>>>>>> from the Ubuntu repository installed with apt-get. First i tried
>>>>>>>>>>> the
>>>>>>>>>>> installation according the wiki http://wiki.apache.org/solr/**
>>>>>>>>>>> SolrJetty <http://wiki.apache.org/solr/****SolrJetty<http://wiki.apache.org/solr/**SolrJetty>
>>>>>>>>>>> <http://wiki.apache.**org/solr/SolrJetty<http://wiki.apache.org/solr/SolrJetty>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>> .
>>>>>>>>>>>>
>>>>>>>>>>> Then
>>>>>>>>>>> i found this example
>>>>>>>>>>> http://www.kingstonlabs.com/******blog/how-to-install-solr-36-**
>>>>>>>>>>> **<http://www.kingstonlabs.com/****blog/how-to-install-solr-36-**>
>>>>>>>>>>> <http://www.kingstonlabs.**com/**blog/how-to-install-**
>>>>>>>>>>> solr-36-**<http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**>
>>>>>>>>>>> >
>>>>>>>>>>> on-ubuntu-1204/and<http://www.****kingstonlabs.com/blog/how-**
>>>>>>>>>>> to-** <http://kingstonlabs.com/blog/how-to-**>
>>>>>>>>>>> install-solr-36-on-ubuntu-****1204/and<http://www.**
>>>>>>>>>>> kingstonlabs.com/blog/how-to-**install-solr-36-on-ubuntu-**
>>>>>>>>>>> 1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>>>>>>>> >
>>>>>>>>>>>
>>>>>>>>>>> tried the Configuration according to the book pache Solr 4
>>>>>>>>>>> Cookbook
>>>>>>>>>>> by
>>>>>>>>>>> Rafal Kuc.
>>>>>>>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on
>>>>>>>>>>> Ubuntus
>>>>>>>>>>> jetty 6.1 :(
>>>>>>>>>>> Can somebody confirm that it's impossible or give me an advice
>>>>>>>>>>> how
>>>>>>>>>>> to
>>>>>>>>>>> run
>>>>>>>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>>>>>>>> Regards
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
OK. I extracted the solr.war in webapps folder. And than out.log reports
2013-10-10 16:47:28.184:WARN::Config error at <New id="ServerLog"
class="java.io.PrintStream"><Arg>| <New
class="org.mortbay.util.RolloverFileOutputStream"><Arg><SystemProperty
name="jetty.home" default="."/>/logs/yyyy_mm_dd.stderrout.log</Arg><Arg
type="boolean">false</Arg><Arg type="int">90</Arg><Arg><Call
class="java.util.TimeZone"
name="getTimeZone"><Arg>GMT</Arg></Call></Arg><Get id="ServerLogName"
name="datedFilename"/></New>| </Arg></New>
java.lang.reflect.InvocationTargetException
2013-10-10 16:47:28.191:WARN::EXCEPTION
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at
org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:608)
at
org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:915)
at org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:837)
at
org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:593)
at
org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:256)
at
org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.mortbay.start.Main.invokeMain(Main.java:194)
at org.mortbay.start.Main.start(Main.java:534)
at org.mortbay.jetty.start.daemon.Bootstrap.start(Bootstrap.java:30)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
2013-10-10 16:47:28.192:WARN::Nested in
java.lang.reflect.InvocationTargetException:
java.io.IOException: Cannot write log file
/var/log/jetty/2013_10_10.stderrout.log
at
org.mortbay.util.RolloverFileOutputStream.setFile(RolloverFileOutputStream.java:233)
at
org.mortbay.util.RolloverFileOutputStream.<init>(RolloverFileOutputStream.java:164)
at
org.mortbay.util.RolloverFileOutputStream.<init>(RolloverFileOutputStream.java:116)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at
org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:608)
at
org.mortbay.xml.XmlConfiguration.itemValue(XmlConfiguration.java:915)
at org.mortbay.xml.XmlConfiguration.value(XmlConfiguration.java:837)
at
org.mortbay.xml.XmlConfiguration.newObj(XmlConfiguration.java:593)
at
org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:256)
at
org.mortbay.xml.XmlConfiguration.configure(XmlConfiguration.java:214)
at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:974)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.mortbay.start.Main.invokeMain(Main.java:194)
at org.mortbay.start.Main.start(Main.java:534)
at org.mortbay.jetty.start.daemon.Bootstrap.start(Bootstrap.java:30)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:177)
2013/10/10 Guido Medina <gu...@temetra.com>
> Add the following jars inside solr.war WEB-INF/lib folder:
>
> jcl-over-slf4j-1.7.5.jar
> jul-to-slf4j-1.7.5.jar
> log4j-1.2.17.jar
> slf4j-api-1.7.5.jar
> slf4j-log4j12-1.7.5.jar
>
> Optional if you are going to use spatial search:
> jts-1.13.jar
>
> Guido.
>
>
> On 10/10/13 14:33, Peter Schmidt wrote:
>
>> Sorry terminal shows:
>>
>> $ sudo service jetty start
>> Found JAVA=/usr/lib/jvm/java-6-**openjdk/jre/bin/java in JAVA_HOME=/
>> Starting Jetty: FAILED
>>
>>
>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>
>> The log:
>>>
>>> 2013-10-10 15:01:47.071:INFO::jetty-6.1.**22
>>> 2013-10-10 15:01:47.110:INFO::Deploy /etc/jetty/contexts/javadoc.**xml
>>> ->
>>> org.mortbay.jetty.handler.**ContextHandler@2353f67e
>>> {/javadoc,file:/usr/share/doc/**libjetty-java/api/}
>>> 2013-10-10 15:01:47.161:INFO::NO JSP Support for , did not find
>>> org.apache.jasper.servlet.**JspServlet
>>> 2013-10-10 15:01:47.192:INFO::Extract file:/var/lib/jetty/webapps/**
>>> solr.war
>>> to /tmp/Jetty_0_0_0_0_8080_solr.**war__solr__7k9npr/webapp
>>> 2013-10-10 15:01:47.761:INFO::NO JSP Support for /solr, did not find
>>> org.apache.jasper.servlet.**JspServlet
>>> 2013-10-10 15:01:47.868:WARN::failed SolrRequestFilter:
>>> org.apache.solr.common.**SolrException: Could not find necessary SLF4j
>>> logging jars. If using Jetty, the SLF4j logging jars need to go in the
>>> jetty lib/ext directory. For other containers, the corresponding
>>> directory
>>> should be used. For more information, see:
>>> http://wiki.apache.org/solr/**SolrLogging<http://wiki.apache.org/solr/SolrLogging>
>>> 2013-10-10 15:01:47.869:WARN::Failed startup of context
>>> org.mortbay.jetty.webapp.**WebAppContext@a13f991
>>> {/solr,file:/var/lib/jetty/**webapps/solr.war}
>>> org.apache.solr.common.**SolrException: Could not find necessary SLF4j
>>> logging jars. If using Jetty, the SLF4j logging jars need to go in the
>>> jetty lib/ext directory. For other containers, the corresponding
>>> directory
>>> should be used. For more information, see:
>>> http://wiki.apache.org/solr/**SolrLogging<http://wiki.apache.org/solr/SolrLogging>
>>> at
>>> org.apache.solr.servlet.**SolrDispatchFilter.<init>(**
>>> SolrDispatchFilter.java:104)
>>> at sun.reflect.**NativeConstructorAccessorImpl.**
>>> newInstance0(Native
>>> Method)
>>> at
>>> sun.reflect.**NativeConstructorAccessorImpl.**newInstance(**
>>> NativeConstructorAccessorImpl.**java:57)
>>> at
>>> sun.reflect.**DelegatingConstructorAccessorI**mpl.newInstance(**
>>> DelegatingConstructorAccessorI**mpl.java:45)
>>> at java.lang.reflect.Constructor.**
>>> newInstance(Constructor.java:**532)
>>> at java.lang.Class.newInstance0(**Class.java:374)
>>> at java.lang.Class.newInstance(**Class.java:327)
>>> at org.mortbay.jetty.servlet.**Holder.newInstance(Holder.**
>>> java:153)
>>> at
>>> org.mortbay.jetty.servlet.**FilterHolder.doStart(**FilterHolder.java:92)
>>> at
>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>> AbstractLifeCycle.java:50)
>>> at
>>> org.mortbay.jetty.servlet.**ServletHandler.initialize(**
>>> ServletHandler.java:662)
>>> at org.mortbay.jetty.servlet.**Context.startContext(Context.**
>>> java:140)
>>> at
>>> org.mortbay.jetty.webapp.**WebAppContext.startContext(**
>>> WebAppContext.java:1250)
>>> at
>>> org.mortbay.jetty.handler.**ContextHandler.doStart(**
>>> ContextHandler.java:518)
>>> at
>>> org.mortbay.jetty.webapp.**WebAppContext.doStart(**
>>> WebAppContext.java:467)
>>> at
>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>> AbstractLifeCycle.java:50)
>>> at
>>> org.mortbay.jetty.handler.**HandlerCollection.doStart(**
>>> HandlerCollection.java:152)
>>> at
>>> org.mortbay.jetty.handler.**ContextHandlerCollection.**doStart(**
>>> ContextHandlerCollection.java:**156)
>>> at
>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>> AbstractLifeCycle.java:50)
>>> at
>>> org.mortbay.jetty.handler.**HandlerCollection.doStart(**
>>> HandlerCollection.java:152)
>>> at
>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>> AbstractLifeCycle.java:50)
>>> at
>>> org.mortbay.jetty.handler.**HandlerWrapper.doStart(**
>>> HandlerWrapper.java:130)
>>> at org.mortbay.jetty.Server.**doStart(Server.java:224)
>>> at
>>> org.mortbay.component.**AbstractLifeCycle.start(**
>>> AbstractLifeCycle.java:50)
>>> at org.mortbay.xml.**XmlConfiguration.main(**
>>> XmlConfiguration.java:985)
>>> at sun.reflect.**NativeMethodAccessorImpl.**invoke0(Native
>>> Method)
>>> at
>>> sun.reflect.**NativeMethodAccessorImpl.**invoke(**
>>> NativeMethodAccessorImpl.java:**57)
>>> at
>>> sun.reflect.**DelegatingMethodAccessorImpl.**invoke(**
>>> DelegatingMethodAccessorImpl.**java:43)
>>> at java.lang.reflect.Method.**invoke(Method.java:616)
>>> at org.mortbay.start.Main.**invokeMain(Main.java:194)
>>> at org.mortbay.start.Main.start(**Main.java:534)
>>> at org.mortbay.start.Main.start(**Main.java:441)
>>> at org.mortbay.start.Main.main(**Main.java:119)
>>> 2013-10-10 15:01:47.870:WARN::failed
>>> org.mortbay.jetty.webapp.**WebAppContext@a13f991{/solr,**
>>> file:/var/lib/jetty/webapps/**solr.war}:
>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>> 2013-10-10 15:01:47.870:WARN::failed ContextHandlerCollection@**
>>> 2565a3c2:
>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>> 2013-10-10 15:01:47.870:INFO::Opened /var/log/jetty/2013_10_10.**
>>> request.log
>>> 2013-10-10 15:01:47.871:WARN::failed HandlerCollection@33e228bc:
>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>> 2013-10-10 15:01:47.871:WARN::Error starting handlers
>>> java.lang.**NoClassDefFoundError: org/slf4j/Logger
>>> at java.lang.Class.**getDeclaredMethods0(Native Method)
>>> at java.lang.Class.**privateGetDeclaredMethods(**
>>> Class.java:2482)
>>> at java.lang.Class.getMethod0(**Class.java:2725)
>>> at java.lang.Class.getMethod(**Class.java:1650)
>>> at org.mortbay.log.Log.unwind(**Log.java:228)
>>> at org.mortbay.log.Log.warn(Log.**java:197)
>>> at
>>> org.mortbay.jetty.webapp.**WebAppContext.doStart(**
>>> WebAppContext.java:475)
>>> ...
>>>
>>> And when i copy the jars from solr-4.4.0/example/lib and
>>> solr-4.4.0/example/lib and solr-4.4.0/example/lib/ext to jettys lib
>>> directory and lib/ext the server is not starting anymore. Quits with
>>> JETTY:
>>> Failed without logging something
>>>
>>>
>>>
>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>
>>> Check the jetty logs, there must be something wrong in your collection
>>>> config, usually if it doesn't start it will tell you there.
>>>>
>>>> And of course, for every change you make be sure you restart jetty.
>>>>
>>>> Guido.
>>>>
>>>>
>>>> On 10/10/13 13:20, Peter Schmidt wrote:
>>>>
>>>> No, it's not working that easy with the jetty 6.1.
>>>>>
>>>>> When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
>>>>> solr.war in the jetty webapps directory i got a 404 when in try to
>>>>> reach
>>>>> http://localhost:8080 or http://localhost:8080/solr.
>>>>>
>>>>>
>>>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>>>
>>>>> My I forgot to mention where you need to copy the solr.war file:
>>>>>
>>>>>> /var/lib/jetty/webapps
>>>>>>
>>>>>> Guido.
>>>>>>
>>>>>>
>>>>>> On 10/10/13 10:48, Guido Medina wrote:
>>>>>>
>>>>>> Here is the pertinent changes you need to pass to
>>>>>> /etc/default/jetty:
>>>>>>
>>>>>>> * JAVA_OPTIONS="-Djava.awt.******headless=true
>>>>>>> -Dfile.encoding=UTF-8
>>>>>>>
>>>>>>>
>>>>>>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>>>>>>> * JAVA_OPTIONS="-Dsolr.solr.******home=$YOUR_SOLR_COLLECTION_***
>>>>>>> ***HOME
>>>>>>>
>>>>>>>
>>>>>>> $JAVA_OPTIONS"
>>>>>>>
>>>>>>>
>>>>>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to
>>>>>>> play
>>>>>>> with it. Adjust your solr collection home to whatever path is on your
>>>>>>> system.
>>>>>>>
>>>>>>> HTH,
>>>>>>>
>>>>>>> Guido.
>>>>>>>
>>>>>>> On 10/10/13 10:43, Guido Medina wrote:
>>>>>>>
>>>>>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
>>>>>>>
>>>>>>>> repo, we have in production for few years now with no issues, you
>>>>>>>> just need
>>>>>>>> to be sure your solr.war has the required jars in it, also your
>>>>>>>> collection
>>>>>>>> must have the extra jars needed by your app.
>>>>>>>>
>>>>>>>> We have been running it in Ubuntu Server 12.04 LTS for a long time,
>>>>>>>> it
>>>>>>>> is easy to have the jetty server with default repo package since it
>>>>>>>> is easy
>>>>>>>> to pass JVM parameters using /etc/default/jetty config file.
>>>>>>>>
>>>>>>>> HTH,
>>>>>>>>
>>>>>>>> Guido.
>>>>>>>>
>>>>>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>>>>>>
>>>>>>>> Do you get an error?
>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>>>>>
>>>>>>>>> Hey folks,
>>>>>>>>>
>>>>>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with
>>>>>>>>>> Jetty
>>>>>>>>>> 6.1
>>>>>>>>>> from the Ubuntu repository installed with apt-get. First i tried
>>>>>>>>>> the
>>>>>>>>>> installation according the wiki http://wiki.apache.org/solr/**
>>>>>>>>>> SolrJetty <http://wiki.apache.org/solr/****SolrJetty<http://wiki.apache.org/solr/**SolrJetty>
>>>>>>>>>> <http://wiki.apache.**org/solr/SolrJetty<http://wiki.apache.org/solr/SolrJetty>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>>> .
>>>>>>>>>>>
>>>>>>>>>> Then
>>>>>>>>>> i found this example
>>>>>>>>>> http://www.kingstonlabs.com/******blog/how-to-install-solr-36-**
>>>>>>>>>> **<http://www.kingstonlabs.com/****blog/how-to-install-solr-36-**>
>>>>>>>>>> <http://www.kingstonlabs.**com/**blog/how-to-install-**solr-36-**<http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**>
>>>>>>>>>> >
>>>>>>>>>> on-ubuntu-1204/and<http://www.****kingstonlabs.com/blog/how-**
>>>>>>>>>> to-** <http://kingstonlabs.com/blog/how-to-**>
>>>>>>>>>> install-solr-36-on-ubuntu-****1204/and<http://www.**
>>>>>>>>>> kingstonlabs.com/blog/how-to-**install-solr-36-on-ubuntu-**
>>>>>>>>>> 1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>>> tried the Configuration according to the book pache Solr 4
>>>>>>>>>> Cookbook
>>>>>>>>>> by
>>>>>>>>>> Rafal Kuc.
>>>>>>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on
>>>>>>>>>> Ubuntus
>>>>>>>>>> jetty 6.1 :(
>>>>>>>>>> Can somebody confirm that it's impossible or give me an advice how
>>>>>>>>>> to
>>>>>>>>>> run
>>>>>>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>>>>>>> Regards
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
Add the following jars inside solr.war WEB-INF/lib folder:
jcl-over-slf4j-1.7.5.jar
jul-to-slf4j-1.7.5.jar
log4j-1.2.17.jar
slf4j-api-1.7.5.jar
slf4j-log4j12-1.7.5.jar
Optional if you are going to use spatial search:
jts-1.13.jar
Guido.
On 10/10/13 14:33, Peter Schmidt wrote:
> Sorry terminal shows:
>
> $ sudo service jetty start
> Found JAVA=/usr/lib/jvm/java-6-openjdk/jre/bin/java in JAVA_HOME=/
> Starting Jetty: FAILED
>
>
> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>
>> The log:
>>
>> 2013-10-10 15:01:47.071:INFO::jetty-6.1.22
>> 2013-10-10 15:01:47.110:INFO::Deploy /etc/jetty/contexts/javadoc.xml ->
>> org.mortbay.jetty.handler.ContextHandler@2353f67e
>> {/javadoc,file:/usr/share/doc/libjetty-java/api/}
>> 2013-10-10 15:01:47.161:INFO::NO JSP Support for , did not find
>> org.apache.jasper.servlet.JspServlet
>> 2013-10-10 15:01:47.192:INFO::Extract file:/var/lib/jetty/webapps/solr.war
>> to /tmp/Jetty_0_0_0_0_8080_solr.war__solr__7k9npr/webapp
>> 2013-10-10 15:01:47.761:INFO::NO JSP Support for /solr, did not find
>> org.apache.jasper.servlet.JspServlet
>> 2013-10-10 15:01:47.868:WARN::failed SolrRequestFilter:
>> org.apache.solr.common.SolrException: Could not find necessary SLF4j
>> logging jars. If using Jetty, the SLF4j logging jars need to go in the
>> jetty lib/ext directory. For other containers, the corresponding directory
>> should be used. For more information, see:
>> http://wiki.apache.org/solr/SolrLogging
>> 2013-10-10 15:01:47.869:WARN::Failed startup of context
>> org.mortbay.jetty.webapp.WebAppContext@a13f991
>> {/solr,file:/var/lib/jetty/webapps/solr.war}
>> org.apache.solr.common.SolrException: Could not find necessary SLF4j
>> logging jars. If using Jetty, the SLF4j logging jars need to go in the
>> jetty lib/ext directory. For other containers, the corresponding directory
>> should be used. For more information, see:
>> http://wiki.apache.org/solr/SolrLogging
>> at
>> org.apache.solr.servlet.SolrDispatchFilter.<init>(SolrDispatchFilter.java:104)
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>> Method)
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>> at java.lang.Class.newInstance0(Class.java:374)
>> at java.lang.Class.newInstance(Class.java:327)
>> at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:153)
>> at
>> org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:92)
>> at
>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>> at
>> org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:662)
>> at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
>> at
>> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
>> at
>> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
>> at
>> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
>> at
>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>> at
>> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
>> at
>> org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
>> at
>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>> at
>> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
>> at
>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>> at
>> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
>> at org.mortbay.jetty.Server.doStart(Server.java:224)
>> at
>> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
>> at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:616)
>> at org.mortbay.start.Main.invokeMain(Main.java:194)
>> at org.mortbay.start.Main.start(Main.java:534)
>> at org.mortbay.start.Main.start(Main.java:441)
>> at org.mortbay.start.Main.main(Main.java:119)
>> 2013-10-10 15:01:47.870:WARN::failed
>> org.mortbay.jetty.webapp.WebAppContext@a13f991{/solr,file:/var/lib/jetty/webapps/solr.war}:
>> java.lang.NoClassDefFoundError: org/slf4j/Logger
>> 2013-10-10 15:01:47.870:WARN::failed ContextHandlerCollection@2565a3c2:
>> java.lang.NoClassDefFoundError: org/slf4j/Logger
>> 2013-10-10 15:01:47.870:INFO::Opened /var/log/jetty/2013_10_10.request.log
>> 2013-10-10 15:01:47.871:WARN::failed HandlerCollection@33e228bc:
>> java.lang.NoClassDefFoundError: org/slf4j/Logger
>> 2013-10-10 15:01:47.871:WARN::Error starting handlers
>> java.lang.NoClassDefFoundError: org/slf4j/Logger
>> at java.lang.Class.getDeclaredMethods0(Native Method)
>> at java.lang.Class.privateGetDeclaredMethods(Class.java:2482)
>> at java.lang.Class.getMethod0(Class.java:2725)
>> at java.lang.Class.getMethod(Class.java:1650)
>> at org.mortbay.log.Log.unwind(Log.java:228)
>> at org.mortbay.log.Log.warn(Log.java:197)
>> at
>> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475)
>> ...
>>
>> And when i copy the jars from solr-4.4.0/example/lib and
>> solr-4.4.0/example/lib and solr-4.4.0/example/lib/ext to jettys lib
>> directory and lib/ext the server is not starting anymore. Quits with JETTY:
>> Failed without logging something
>>
>>
>>
>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>
>>> Check the jetty logs, there must be something wrong in your collection
>>> config, usually if it doesn't start it will tell you there.
>>>
>>> And of course, for every change you make be sure you restart jetty.
>>>
>>> Guido.
>>>
>>>
>>> On 10/10/13 13:20, Peter Schmidt wrote:
>>>
>>>> No, it's not working that easy with the jetty 6.1.
>>>>
>>>> When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
>>>> solr.war in the jetty webapps directory i got a 404 when in try to reach
>>>> http://localhost:8080 or http://localhost:8080/solr.
>>>>
>>>>
>>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>>
>>>> My I forgot to mention where you need to copy the solr.war file:
>>>>> /var/lib/jetty/webapps
>>>>>
>>>>> Guido.
>>>>>
>>>>>
>>>>> On 10/10/13 10:48, Guido Medina wrote:
>>>>>
>>>>> Here is the pertinent changes you need to pass to /etc/default/jetty:
>>>>>> * JAVA_OPTIONS="-Djava.awt.****headless=true -Dfile.encoding=UTF-8
>>>>>>
>>>>>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>>>>>> * JAVA_OPTIONS="-Dsolr.solr.****home=$YOUR_SOLR_COLLECTION_****HOME
>>>>>>
>>>>>> $JAVA_OPTIONS"
>>>>>>
>>>>>>
>>>>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to
>>>>>> play
>>>>>> with it. Adjust your solr collection home to whatever path is on your
>>>>>> system.
>>>>>>
>>>>>> HTH,
>>>>>>
>>>>>> Guido.
>>>>>>
>>>>>> On 10/10/13 10:43, Guido Medina wrote:
>>>>>>
>>>>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
>>>>>>> repo, we have in production for few years now with no issues, you
>>>>>>> just need
>>>>>>> to be sure your solr.war has the required jars in it, also your
>>>>>>> collection
>>>>>>> must have the extra jars needed by your app.
>>>>>>>
>>>>>>> We have been running it in Ubuntu Server 12.04 LTS for a long time, it
>>>>>>> is easy to have the jetty server with default repo package since it
>>>>>>> is easy
>>>>>>> to pass JVM parameters using /etc/default/jetty config file.
>>>>>>>
>>>>>>> HTH,
>>>>>>>
>>>>>>> Guido.
>>>>>>>
>>>>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>>>>>
>>>>>>> Do you get an error?
>>>>>>>>
>>>>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>>>>
>>>>>>>> Hey folks,
>>>>>>>>
>>>>>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with
>>>>>>>>> Jetty
>>>>>>>>> 6.1
>>>>>>>>> from the Ubuntu repository installed with apt-get. First i tried the
>>>>>>>>> installation according the wiki http://wiki.apache.org/solr/**
>>>>>>>>> SolrJetty <http://wiki.apache.org/solr/**SolrJetty<http://wiki.apache.org/solr/SolrJetty>
>>>>>>>>>> .
>>>>>>>>> Then
>>>>>>>>> i found this example
>>>>>>>>> http://www.kingstonlabs.com/****blog/how-to-install-solr-36-**<http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**>
>>>>>>>>> on-ubuntu-1204/and<http://www.**kingstonlabs.com/blog/how-to-**
>>>>>>>>> install-solr-36-on-ubuntu-**1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>>>>>> tried the Configuration according to the book pache Solr 4 Cookbook
>>>>>>>>> by
>>>>>>>>> Rafal Kuc.
>>>>>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on
>>>>>>>>> Ubuntus
>>>>>>>>> jetty 6.1 :(
>>>>>>>>> Can somebody confirm that it's impossible or give me an advice how
>>>>>>>>> to
>>>>>>>>> run
>>>>>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>>>>>> Regards
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
Sorry terminal shows:
$ sudo service jetty start
Found JAVA=/usr/lib/jvm/java-6-openjdk/jre/bin/java in JAVA_HOME=/
Starting Jetty: FAILED
2013/10/10 Peter Schmidt <pe...@gmail.com>
> The log:
>
> 2013-10-10 15:01:47.071:INFO::jetty-6.1.22
> 2013-10-10 15:01:47.110:INFO::Deploy /etc/jetty/contexts/javadoc.xml ->
> org.mortbay.jetty.handler.ContextHandler@2353f67e
> {/javadoc,file:/usr/share/doc/libjetty-java/api/}
> 2013-10-10 15:01:47.161:INFO::NO JSP Support for , did not find
> org.apache.jasper.servlet.JspServlet
> 2013-10-10 15:01:47.192:INFO::Extract file:/var/lib/jetty/webapps/solr.war
> to /tmp/Jetty_0_0_0_0_8080_solr.war__solr__7k9npr/webapp
> 2013-10-10 15:01:47.761:INFO::NO JSP Support for /solr, did not find
> org.apache.jasper.servlet.JspServlet
> 2013-10-10 15:01:47.868:WARN::failed SolrRequestFilter:
> org.apache.solr.common.SolrException: Could not find necessary SLF4j
> logging jars. If using Jetty, the SLF4j logging jars need to go in the
> jetty lib/ext directory. For other containers, the corresponding directory
> should be used. For more information, see:
> http://wiki.apache.org/solr/SolrLogging
> 2013-10-10 15:01:47.869:WARN::Failed startup of context
> org.mortbay.jetty.webapp.WebAppContext@a13f991
> {/solr,file:/var/lib/jetty/webapps/solr.war}
> org.apache.solr.common.SolrException: Could not find necessary SLF4j
> logging jars. If using Jetty, the SLF4j logging jars need to go in the
> jetty lib/ext directory. For other containers, the corresponding directory
> should be used. For more information, see:
> http://wiki.apache.org/solr/SolrLogging
> at
> org.apache.solr.servlet.SolrDispatchFilter.<init>(SolrDispatchFilter.java:104)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> at java.lang.Class.newInstance0(Class.java:374)
> at java.lang.Class.newInstance(Class.java:327)
> at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:153)
> at
> org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:92)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:662)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
> at
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
> at
> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
> at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:224)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.mortbay.start.Main.invokeMain(Main.java:194)
> at org.mortbay.start.Main.start(Main.java:534)
> at org.mortbay.start.Main.start(Main.java:441)
> at org.mortbay.start.Main.main(Main.java:119)
> 2013-10-10 15:01:47.870:WARN::failed
> org.mortbay.jetty.webapp.WebAppContext@a13f991{/solr,file:/var/lib/jetty/webapps/solr.war}:
> java.lang.NoClassDefFoundError: org/slf4j/Logger
> 2013-10-10 15:01:47.870:WARN::failed ContextHandlerCollection@2565a3c2:
> java.lang.NoClassDefFoundError: org/slf4j/Logger
> 2013-10-10 15:01:47.870:INFO::Opened /var/log/jetty/2013_10_10.request.log
> 2013-10-10 15:01:47.871:WARN::failed HandlerCollection@33e228bc:
> java.lang.NoClassDefFoundError: org/slf4j/Logger
> 2013-10-10 15:01:47.871:WARN::Error starting handlers
> java.lang.NoClassDefFoundError: org/slf4j/Logger
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2482)
> at java.lang.Class.getMethod0(Class.java:2725)
> at java.lang.Class.getMethod(Class.java:1650)
> at org.mortbay.log.Log.unwind(Log.java:228)
> at org.mortbay.log.Log.warn(Log.java:197)
> at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475)
> ...
>
> And when i copy the jars from solr-4.4.0/example/lib and
> solr-4.4.0/example/lib and solr-4.4.0/example/lib/ext to jettys lib
> directory and lib/ext the server is not starting anymore. Quits with JETTY:
> Failed without logging something
>
>
>
> 2013/10/10 Guido Medina <gu...@temetra.com>
>
>> Check the jetty logs, there must be something wrong in your collection
>> config, usually if it doesn't start it will tell you there.
>>
>> And of course, for every change you make be sure you restart jetty.
>>
>> Guido.
>>
>>
>> On 10/10/13 13:20, Peter Schmidt wrote:
>>
>>> No, it's not working that easy with the jetty 6.1.
>>>
>>> When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
>>> solr.war in the jetty webapps directory i got a 404 when in try to reach
>>> http://localhost:8080 or http://localhost:8080/solr.
>>>
>>>
>>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>>
>>> My I forgot to mention where you need to copy the solr.war file:
>>>>
>>>> /var/lib/jetty/webapps
>>>>
>>>> Guido.
>>>>
>>>>
>>>> On 10/10/13 10:48, Guido Medina wrote:
>>>>
>>>> Here is the pertinent changes you need to pass to /etc/default/jetty:
>>>>>
>>>>> * JAVA_OPTIONS="-Djava.awt.****headless=true -Dfile.encoding=UTF-8
>>>>>
>>>>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>>>>> * JAVA_OPTIONS="-Dsolr.solr.****home=$YOUR_SOLR_COLLECTION_****HOME
>>>>>
>>>>> $JAVA_OPTIONS"
>>>>>
>>>>>
>>>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to
>>>>> play
>>>>> with it. Adjust your solr collection home to whatever path is on your
>>>>> system.
>>>>>
>>>>> HTH,
>>>>>
>>>>> Guido.
>>>>>
>>>>> On 10/10/13 10:43, Guido Medina wrote:
>>>>>
>>>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
>>>>>> repo, we have in production for few years now with no issues, you
>>>>>> just need
>>>>>> to be sure your solr.war has the required jars in it, also your
>>>>>> collection
>>>>>> must have the extra jars needed by your app.
>>>>>>
>>>>>> We have been running it in Ubuntu Server 12.04 LTS for a long time, it
>>>>>> is easy to have the jetty server with default repo package since it
>>>>>> is easy
>>>>>> to pass JVM parameters using /etc/default/jetty config file.
>>>>>>
>>>>>> HTH,
>>>>>>
>>>>>> Guido.
>>>>>>
>>>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>>>>
>>>>>> Do you get an error?
>>>>>>>
>>>>>>>
>>>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>>>
>>>>>>> Hey folks,
>>>>>>>
>>>>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with
>>>>>>>> Jetty
>>>>>>>> 6.1
>>>>>>>> from the Ubuntu repository installed with apt-get. First i tried the
>>>>>>>> installation according the wiki http://wiki.apache.org/solr/**
>>>>>>>> SolrJetty <http://wiki.apache.org/solr/**SolrJetty<http://wiki.apache.org/solr/SolrJetty>
>>>>>>>> >.
>>>>>>>>
>>>>>>>> Then
>>>>>>>> i found this example
>>>>>>>> http://www.kingstonlabs.com/****blog/how-to-install-solr-36-**<http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**>
>>>>>>>> on-ubuntu-1204/and<http://www.**kingstonlabs.com/blog/how-to-**
>>>>>>>> install-solr-36-on-ubuntu-**1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>>>>> >
>>>>>>>>
>>>>>>>> tried the Configuration according to the book pache Solr 4 Cookbook
>>>>>>>> by
>>>>>>>> Rafal Kuc.
>>>>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on
>>>>>>>> Ubuntus
>>>>>>>> jetty 6.1 :(
>>>>>>>> Can somebody confirm that it's impossible or give me an advice how
>>>>>>>> to
>>>>>>>> run
>>>>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>>>>> Regards
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
The log:
2013-10-10 15:01:47.071:INFO::jetty-6.1.22
2013-10-10 15:01:47.110:INFO::Deploy /etc/jetty/contexts/javadoc.xml ->
org.mortbay.jetty.handler.ContextHandler@2353f67e
{/javadoc,file:/usr/share/doc/libjetty-java/api/}
2013-10-10 15:01:47.161:INFO::NO JSP Support for , did not find
org.apache.jasper.servlet.JspServlet
2013-10-10 15:01:47.192:INFO::Extract file:/var/lib/jetty/webapps/solr.war
to /tmp/Jetty_0_0_0_0_8080_solr.war__solr__7k9npr/webapp
2013-10-10 15:01:47.761:INFO::NO JSP Support for /solr, did not find
org.apache.jasper.servlet.JspServlet
2013-10-10 15:01:47.868:WARN::failed SolrRequestFilter:
org.apache.solr.common.SolrException: Could not find necessary SLF4j
logging jars. If using Jetty, the SLF4j logging jars need to go in the
jetty lib/ext directory. For other containers, the corresponding directory
should be used. For more information, see:
http://wiki.apache.org/solr/SolrLogging
2013-10-10 15:01:47.869:WARN::Failed startup of context
org.mortbay.jetty.webapp.WebAppContext@a13f991
{/solr,file:/var/lib/jetty/webapps/solr.war}
org.apache.solr.common.SolrException: Could not find necessary SLF4j
logging jars. If using Jetty, the SLF4j logging jars need to go in the
jetty lib/ext directory. For other containers, the corresponding directory
should be used. For more information, see:
http://wiki.apache.org/solr/SolrLogging
at
org.apache.solr.servlet.SolrDispatchFilter.<init>(SolrDispatchFilter.java:104)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
at java.lang.Class.newInstance0(Class.java:374)
at java.lang.Class.newInstance(Class.java:327)
at org.mortbay.jetty.servlet.Holder.newInstance(Holder.java:153)
at
org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:92)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:662)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.mortbay.start.Main.invokeMain(Main.java:194)
at org.mortbay.start.Main.start(Main.java:534)
at org.mortbay.start.Main.start(Main.java:441)
at org.mortbay.start.Main.main(Main.java:119)
2013-10-10 15:01:47.870:WARN::failed
org.mortbay.jetty.webapp.WebAppContext@a13f991{/solr,file:/var/lib/jetty/webapps/solr.war}:
java.lang.NoClassDefFoundError: org/slf4j/Logger
2013-10-10 15:01:47.870:WARN::failed ContextHandlerCollection@2565a3c2:
java.lang.NoClassDefFoundError: org/slf4j/Logger
2013-10-10 15:01:47.870:INFO::Opened /var/log/jetty/2013_10_10.request.log
2013-10-10 15:01:47.871:WARN::failed HandlerCollection@33e228bc:
java.lang.NoClassDefFoundError: org/slf4j/Logger
2013-10-10 15:01:47.871:WARN::Error starting handlers
java.lang.NoClassDefFoundError: org/slf4j/Logger
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2482)
at java.lang.Class.getMethod0(Class.java:2725)
at java.lang.Class.getMethod(Class.java:1650)
at org.mortbay.log.Log.unwind(Log.java:228)
at org.mortbay.log.Log.warn(Log.java:197)
at
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:475)
...
And when i copy the jars from solr-4.4.0/example/lib and
solr-4.4.0/example/lib and solr-4.4.0/example/lib/ext to jettys lib
directory and lib/ext the server is not starting anymore. Quits with JETTY:
Failed without logging something
2013/10/10 Guido Medina <gu...@temetra.com>
> Check the jetty logs, there must be something wrong in your collection
> config, usually if it doesn't start it will tell you there.
>
> And of course, for every change you make be sure you restart jetty.
>
> Guido.
>
>
> On 10/10/13 13:20, Peter Schmidt wrote:
>
>> No, it's not working that easy with the jetty 6.1.
>>
>> When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
>> solr.war in the jetty webapps directory i got a 404 when in try to reach
>> http://localhost:8080 or http://localhost:8080/solr.
>>
>>
>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>
>> My I forgot to mention where you need to copy the solr.war file:
>>>
>>> /var/lib/jetty/webapps
>>>
>>> Guido.
>>>
>>>
>>> On 10/10/13 10:48, Guido Medina wrote:
>>>
>>> Here is the pertinent changes you need to pass to /etc/default/jetty:
>>>>
>>>> * JAVA_OPTIONS="-Djava.awt.****headless=true -Dfile.encoding=UTF-8
>>>>
>>>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>>>> * JAVA_OPTIONS="-Dsolr.solr.****home=$YOUR_SOLR_COLLECTION_****HOME
>>>>
>>>> $JAVA_OPTIONS"
>>>>
>>>>
>>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to play
>>>> with it. Adjust your solr collection home to whatever path is on your
>>>> system.
>>>>
>>>> HTH,
>>>>
>>>> Guido.
>>>>
>>>> On 10/10/13 10:43, Guido Medina wrote:
>>>>
>>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
>>>>> repo, we have in production for few years now with no issues, you just
>>>>> need
>>>>> to be sure your solr.war has the required jars in it, also your
>>>>> collection
>>>>> must have the extra jars needed by your app.
>>>>>
>>>>> We have been running it in Ubuntu Server 12.04 LTS for a long time, it
>>>>> is easy to have the jetty server with default repo package since it is
>>>>> easy
>>>>> to pass JVM parameters using /etc/default/jetty config file.
>>>>>
>>>>> HTH,
>>>>>
>>>>> Guido.
>>>>>
>>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>>>
>>>>> Do you get an error?
>>>>>>
>>>>>>
>>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>>
>>>>>> Hey folks,
>>>>>>
>>>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with
>>>>>>> Jetty
>>>>>>> 6.1
>>>>>>> from the Ubuntu repository installed with apt-get. First i tried the
>>>>>>> installation according the wiki http://wiki.apache.org/solr/**
>>>>>>> SolrJetty <http://wiki.apache.org/solr/**SolrJetty<http://wiki.apache.org/solr/SolrJetty>
>>>>>>> >.
>>>>>>>
>>>>>>> Then
>>>>>>> i found this example
>>>>>>> http://www.kingstonlabs.com/****blog/how-to-install-solr-36-**<http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**>
>>>>>>> on-ubuntu-1204/and<http://www.**kingstonlabs.com/blog/how-to-**
>>>>>>> install-solr-36-on-ubuntu-**1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>>>> >
>>>>>>>
>>>>>>> tried the Configuration according to the book pache Solr 4 Cookbook
>>>>>>> by
>>>>>>> Rafal Kuc.
>>>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on
>>>>>>> Ubuntus
>>>>>>> jetty 6.1 :(
>>>>>>> Can somebody confirm that it's impossible or give me an advice how to
>>>>>>> run
>>>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>>>> Regards
>>>>>>>
>>>>>>>
>>>>>>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
On the config I pasted here, Solr mailing list is inserting "**" in
between dots so make sure you remove those.
Example:
JAVA_OPTIONS="-Dsolr.solr.**home=$YOUR_SOLR_COLLECTION_**HOME
$JAVA_OPTIONS"
is really:
JAVA_OPTIONS="-Dsolr . solr . home=$YOUR _ SOLR _ COLLECTION _ HOME
$JAVA_OPTIONS"
Guido.
On 10/10/13 13:51, Guido Medina wrote:
> Check the jetty logs, there must be something wrong in your collection
> config, usually if it doesn't start it will tell you there.
>
> And of course, for every change you make be sure you restart jetty.
>
> Guido.
>
> On 10/10/13 13:20, Peter Schmidt wrote:
>> No, it's not working that easy with the jetty 6.1.
>>
>> When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
>> solr.war in the jetty webapps directory i got a 404 when in try to reach
>> http://localhost:8080 or http://localhost:8080/solr.
>>
>>
>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>
>>> My I forgot to mention where you need to copy the solr.war file:
>>>
>>> /var/lib/jetty/webapps
>>>
>>> Guido.
>>>
>>>
>>> On 10/10/13 10:48, Guido Medina wrote:
>>>
>>>> Here is the pertinent changes you need to pass to /etc/default/jetty:
>>>>
>>>> * JAVA_OPTIONS="-Djava.awt.**headless=true -Dfile.encoding=UTF-8
>>>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>>>> * JAVA_OPTIONS="-Dsolr.solr.**home=$YOUR_SOLR_COLLECTION_**HOME
>>>> $JAVA_OPTIONS"
>>>>
>>>>
>>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to
>>>> play
>>>> with it. Adjust your solr collection home to whatever path is on your
>>>> system.
>>>>
>>>> HTH,
>>>>
>>>> Guido.
>>>>
>>>> On 10/10/13 10:43, Guido Medina wrote:
>>>>
>>>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
>>>>> repo, we have in production for few years now with no issues, you
>>>>> just need
>>>>> to be sure your solr.war has the required jars in it, also your
>>>>> collection
>>>>> must have the extra jars needed by your app.
>>>>>
>>>>> We have been running it in Ubuntu Server 12.04 LTS for a long
>>>>> time, it
>>>>> is easy to have the jetty server with default repo package since
>>>>> it is easy
>>>>> to pass JVM parameters using /etc/default/jetty config file.
>>>>>
>>>>> HTH,
>>>>>
>>>>> Guido.
>>>>>
>>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>>>
>>>>>> Do you get an error?
>>>>>>
>>>>>>
>>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>>
>>>>>> Hey folks,
>>>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with
>>>>>>> Jetty
>>>>>>> 6.1
>>>>>>> from the Ubuntu repository installed with apt-get. First i tried
>>>>>>> the
>>>>>>> installation according the wiki http://wiki.apache.org/solr/**
>>>>>>> SolrJetty <http://wiki.apache.org/solr/SolrJetty>.
>>>>>>> Then
>>>>>>> i found this example
>>>>>>> http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**
>>>>>>> on-ubuntu-1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>>>>
>>>>>>> tried the Configuration according to the book pache Solr 4
>>>>>>> Cookbook by
>>>>>>> Rafal Kuc.
>>>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on
>>>>>>> Ubuntus
>>>>>>> jetty 6.1 :(
>>>>>>> Can somebody confirm that it's impossible or give me an advice
>>>>>>> how to
>>>>>>> run
>>>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>>>> Regards
>>>>>>>
>>>>>>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
Check the jetty logs, there must be something wrong in your collection
config, usually if it doesn't start it will tell you there.
And of course, for every change you make be sure you restart jetty.
Guido.
On 10/10/13 13:20, Peter Schmidt wrote:
> No, it's not working that easy with the jetty 6.1.
>
> When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
> solr.war in the jetty webapps directory i got a 404 when in try to reach
> http://localhost:8080 or http://localhost:8080/solr.
>
>
> 2013/10/10 Guido Medina <gu...@temetra.com>
>
>> My I forgot to mention where you need to copy the solr.war file:
>>
>> /var/lib/jetty/webapps
>>
>> Guido.
>>
>>
>> On 10/10/13 10:48, Guido Medina wrote:
>>
>>> Here is the pertinent changes you need to pass to /etc/default/jetty:
>>>
>>> * JAVA_OPTIONS="-Djava.awt.**headless=true -Dfile.encoding=UTF-8
>>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>>> * JAVA_OPTIONS="-Dsolr.solr.**home=$YOUR_SOLR_COLLECTION_**HOME
>>> $JAVA_OPTIONS"
>>>
>>>
>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to play
>>> with it. Adjust your solr collection home to whatever path is on your
>>> system.
>>>
>>> HTH,
>>>
>>> Guido.
>>>
>>> On 10/10/13 10:43, Guido Medina wrote:
>>>
>>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
>>>> repo, we have in production for few years now with no issues, you just need
>>>> to be sure your solr.war has the required jars in it, also your collection
>>>> must have the extra jars needed by your app.
>>>>
>>>> We have been running it in Ubuntu Server 12.04 LTS for a long time, it
>>>> is easy to have the jetty server with default repo package since it is easy
>>>> to pass JVM parameters using /etc/default/jetty config file.
>>>>
>>>> HTH,
>>>>
>>>> Guido.
>>>>
>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>>
>>>>> Do you get an error?
>>>>>
>>>>>
>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>
>>>>> Hey folks,
>>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with Jetty
>>>>>> 6.1
>>>>>> from the Ubuntu repository installed with apt-get. First i tried the
>>>>>> installation according the wiki http://wiki.apache.org/solr/**
>>>>>> SolrJetty <http://wiki.apache.org/solr/SolrJetty>.
>>>>>> Then
>>>>>> i found this example
>>>>>> http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**
>>>>>> on-ubuntu-1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>>> tried the Configuration according to the book pache Solr 4 Cookbook by
>>>>>> Rafal Kuc.
>>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on Ubuntus
>>>>>> jetty 6.1 :(
>>>>>> Can somebody confirm that it's impossible or give me an advice how to
>>>>>> run
>>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>>> Regards
>>>>>>
>>>>>>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Furkan KAMACI <fu...@gmail.com>.
Did you check here as your logs says:
http://wiki.apache.org/solr/SolrLogging
You have NoClassDefFoundError: error for org/slf4j/Logger and this is
because of there is a dependency mismatch at your libraries.
2013/10/10 Peter Schmidt <pe...@gmail.com>
> >>For repo Jetty (6.1.x) this is a good guide, which is very similar to
> what we have on our environments:
>
> >>http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/<
> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/>
>
> Guido, i used this guide and ended up with the Page not found 404 problem
> like the others (in the comments)
>
> Only solution there is:
>
> Karel<
> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/#>
> vjnunez<
> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/#comment-926517600
> >
>
> * 4 months ago<
> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/#comment-926795805
> >
>
> - -<
> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/#>
> -
>
> I used a different howto for installing jetty 9 from source with solr 4.3.0
> on Ubuntu 13.04 (google it, can't remember the site). Worked for my 12.04
> LTS install, so for me this problem is "fixed".
>
>
>
> 2013/10/10 Guido Medina <gu...@temetra.com>
>
> > For repo Jetty (6.1.x) this is a good guide, which is very similar to
> what
> > we have on our environments:
> >
> > http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**
> > on-ubuntu-1204/<
> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/>
> >
> >
> > Guido.
> >
> > On 10/10/13 13:20, Peter Schmidt wrote:
> >
> >> No, it's not working that easy with the jetty 6.1.
> >>
> >> When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
> >> solr.war in the jetty webapps directory i got a 404 when in try to reach
> >> http://localhost:8080 or http://localhost:8080/solr.
> >>
> >>
> >> 2013/10/10 Guido Medina <gu...@temetra.com>
> >>
> >> My I forgot to mention where you need to copy the solr.war file:
> >>>
> >>> /var/lib/jetty/webapps
> >>>
> >>> Guido.
> >>>
> >>>
> >>> On 10/10/13 10:48, Guido Medina wrote:
> >>>
> >>> Here is the pertinent changes you need to pass to /etc/default/jetty:
> >>>>
> >>>> * JAVA_OPTIONS="-Djava.awt.****headless=true -Dfile.encoding=UTF-8
> >>>>
> >>>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
> >>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
> >>>> * JAVA_OPTIONS="-Dsolr.solr.****home=$YOUR_SOLR_COLLECTION_****HOME
> >>>>
> >>>> $JAVA_OPTIONS"
> >>>>
> >>>>
> >>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to
> play
> >>>> with it. Adjust your solr collection home to whatever path is on your
> >>>> system.
> >>>>
> >>>> HTH,
> >>>>
> >>>> Guido.
> >>>>
> >>>> On 10/10/13 10:43, Guido Medina wrote:
> >>>>
> >>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
> >>>>> repo, we have in production for few years now with no issues, you
> just
> >>>>> need
> >>>>> to be sure your solr.war has the required jars in it, also your
> >>>>> collection
> >>>>> must have the extra jars needed by your app.
> >>>>>
> >>>>> We have been running it in Ubuntu Server 12.04 LTS for a long time,
> it
> >>>>> is easy to have the jetty server with default repo package since it
> is
> >>>>> easy
> >>>>> to pass JVM parameters using /etc/default/jetty config file.
> >>>>>
> >>>>> HTH,
> >>>>>
> >>>>> Guido.
> >>>>>
> >>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
> >>>>>
> >>>>> Do you get an error?
> >>>>>>
> >>>>>>
> >>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
> >>>>>>
> >>>>>> Hey folks,
> >>>>>>
> >>>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with
> >>>>>>> Jetty
> >>>>>>> 6.1
> >>>>>>> from the Ubuntu repository installed with apt-get. First i tried
> the
> >>>>>>> installation according the wiki http://wiki.apache.org/solr/**
> >>>>>>> SolrJetty <http://wiki.apache.org/solr/**SolrJetty<
> http://wiki.apache.org/solr/SolrJetty>
> >>>>>>> >.
> >>>>>>> Then
> >>>>>>> i found this example
> >>>>>>> http://www.kingstonlabs.com/****blog/how-to-install-solr-36-**<
> http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**>
> >>>>>>> on-ubuntu-1204/and<http://www.**kingstonlabs.com/blog/how-to-**
> >>>>>>> install-solr-36-on-ubuntu-**1204/and<
> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and
> >
> >>>>>>> >
> >>>>>>>
> >>>>>>> tried the Configuration according to the book pache Solr 4 Cookbook
> >>>>>>> by
> >>>>>>> Rafal Kuc.
> >>>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on
> >>>>>>> Ubuntus
> >>>>>>> jetty 6.1 :(
> >>>>>>> Can somebody confirm that it's impossible or give me an advice how
> to
> >>>>>>> run
> >>>>>>> Solr 4.4.0 on Jetty 6.1?
> >>>>>>> Regards
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
>>For repo Jetty (6.1.x) this is a good guide, which is very similar to
what we have on our environments:
>>http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/>
Guido, i used this guide and ended up with the Page not found 404 problem
like the others (in the comments)
Only solution there is:
Karel<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/#>
vjnunez<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/#comment-926517600>
* 4 months ago<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/#comment-926795805>
- -<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/#>
-
I used a different howto for installing jetty 9 from source with solr 4.3.0
on Ubuntu 13.04 (google it, can't remember the site). Worked for my 12.04
LTS install, so for me this problem is "fixed".
2013/10/10 Guido Medina <gu...@temetra.com>
> For repo Jetty (6.1.x) this is a good guide, which is very similar to what
> we have on our environments:
>
> http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**
> on-ubuntu-1204/<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/>
>
>
> Guido.
>
> On 10/10/13 13:20, Peter Schmidt wrote:
>
>> No, it's not working that easy with the jetty 6.1.
>>
>> When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
>> solr.war in the jetty webapps directory i got a 404 when in try to reach
>> http://localhost:8080 or http://localhost:8080/solr.
>>
>>
>> 2013/10/10 Guido Medina <gu...@temetra.com>
>>
>> My I forgot to mention where you need to copy the solr.war file:
>>>
>>> /var/lib/jetty/webapps
>>>
>>> Guido.
>>>
>>>
>>> On 10/10/13 10:48, Guido Medina wrote:
>>>
>>> Here is the pertinent changes you need to pass to /etc/default/jetty:
>>>>
>>>> * JAVA_OPTIONS="-Djava.awt.****headless=true -Dfile.encoding=UTF-8
>>>>
>>>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>>>> * JAVA_OPTIONS="-Dsolr.solr.****home=$YOUR_SOLR_COLLECTION_****HOME
>>>>
>>>> $JAVA_OPTIONS"
>>>>
>>>>
>>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to play
>>>> with it. Adjust your solr collection home to whatever path is on your
>>>> system.
>>>>
>>>> HTH,
>>>>
>>>> Guido.
>>>>
>>>> On 10/10/13 10:43, Guido Medina wrote:
>>>>
>>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
>>>>> repo, we have in production for few years now with no issues, you just
>>>>> need
>>>>> to be sure your solr.war has the required jars in it, also your
>>>>> collection
>>>>> must have the extra jars needed by your app.
>>>>>
>>>>> We have been running it in Ubuntu Server 12.04 LTS for a long time, it
>>>>> is easy to have the jetty server with default repo package since it is
>>>>> easy
>>>>> to pass JVM parameters using /etc/default/jetty config file.
>>>>>
>>>>> HTH,
>>>>>
>>>>> Guido.
>>>>>
>>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>>>
>>>>> Do you get an error?
>>>>>>
>>>>>>
>>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>>
>>>>>> Hey folks,
>>>>>>
>>>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with
>>>>>>> Jetty
>>>>>>> 6.1
>>>>>>> from the Ubuntu repository installed with apt-get. First i tried the
>>>>>>> installation according the wiki http://wiki.apache.org/solr/**
>>>>>>> SolrJetty <http://wiki.apache.org/solr/**SolrJetty<http://wiki.apache.org/solr/SolrJetty>
>>>>>>> >.
>>>>>>> Then
>>>>>>> i found this example
>>>>>>> http://www.kingstonlabs.com/****blog/how-to-install-solr-36-**<http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**>
>>>>>>> on-ubuntu-1204/and<http://www.**kingstonlabs.com/blog/how-to-**
>>>>>>> install-solr-36-on-ubuntu-**1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>>>> >
>>>>>>>
>>>>>>> tried the Configuration according to the book pache Solr 4 Cookbook
>>>>>>> by
>>>>>>> Rafal Kuc.
>>>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on
>>>>>>> Ubuntus
>>>>>>> jetty 6.1 :(
>>>>>>> Can somebody confirm that it's impossible or give me an advice how to
>>>>>>> run
>>>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>>>> Regards
>>>>>>>
>>>>>>>
>>>>>>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
For repo Jetty (6.1.x) this is a good guide, which is very similar to
what we have on our environments:
http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/
Guido.
On 10/10/13 13:20, Peter Schmidt wrote:
> No, it's not working that easy with the jetty 6.1.
>
> When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
> solr.war in the jetty webapps directory i got a 404 when in try to reach
> http://localhost:8080 or http://localhost:8080/solr.
>
>
> 2013/10/10 Guido Medina <gu...@temetra.com>
>
>> My I forgot to mention where you need to copy the solr.war file:
>>
>> /var/lib/jetty/webapps
>>
>> Guido.
>>
>>
>> On 10/10/13 10:48, Guido Medina wrote:
>>
>>> Here is the pertinent changes you need to pass to /etc/default/jetty:
>>>
>>> * JAVA_OPTIONS="-Djava.awt.**headless=true -Dfile.encoding=UTF-8
>>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>>> * JAVA_OPTIONS="-Dsolr.solr.**home=$YOUR_SOLR_COLLECTION_**HOME
>>> $JAVA_OPTIONS"
>>>
>>>
>>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to play
>>> with it. Adjust your solr collection home to whatever path is on your
>>> system.
>>>
>>> HTH,
>>>
>>> Guido.
>>>
>>> On 10/10/13 10:43, Guido Medina wrote:
>>>
>>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
>>>> repo, we have in production for few years now with no issues, you just need
>>>> to be sure your solr.war has the required jars in it, also your collection
>>>> must have the extra jars needed by your app.
>>>>
>>>> We have been running it in Ubuntu Server 12.04 LTS for a long time, it
>>>> is easy to have the jetty server with default repo package since it is easy
>>>> to pass JVM parameters using /etc/default/jetty config file.
>>>>
>>>> HTH,
>>>>
>>>> Guido.
>>>>
>>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>>
>>>>> Do you get an error?
>>>>>
>>>>>
>>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>>
>>>>> Hey folks,
>>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with Jetty
>>>>>> 6.1
>>>>>> from the Ubuntu repository installed with apt-get. First i tried the
>>>>>> installation according the wiki http://wiki.apache.org/solr/**
>>>>>> SolrJetty <http://wiki.apache.org/solr/SolrJetty>.
>>>>>> Then
>>>>>> i found this example
>>>>>> http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**
>>>>>> on-ubuntu-1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>>> tried the Configuration according to the book pache Solr 4 Cookbook by
>>>>>> Rafal Kuc.
>>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on Ubuntus
>>>>>> jetty 6.1 :(
>>>>>> Can somebody confirm that it's impossible or give me an advice how to
>>>>>> run
>>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>>> Regards
>>>>>>
>>>>>>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Peter Schmidt <pe...@gmail.com>.
No, it's not working that easy with the jetty 6.1.
When i just add -Dsolr.solr.home to my /etc/default/jetty and put the
solr.war in the jetty webapps directory i got a 404 when in try to reach
http://localhost:8080 or http://localhost:8080/solr.
2013/10/10 Guido Medina <gu...@temetra.com>
> My I forgot to mention where you need to copy the solr.war file:
>
> /var/lib/jetty/webapps
>
> Guido.
>
>
> On 10/10/13 10:48, Guido Medina wrote:
>
>> Here is the pertinent changes you need to pass to /etc/default/jetty:
>>
>> * JAVA_OPTIONS="-Djava.awt.**headless=true -Dfile.encoding=UTF-8
>> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
>> -XX:+OptimizeStringConcat -XX:+UseStringCache"
>> * JAVA_OPTIONS="-Dsolr.solr.**home=$YOUR_SOLR_COLLECTION_**HOME
>> $JAVA_OPTIONS"
>>
>>
>> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to play
>> with it. Adjust your solr collection home to whatever path is on your
>> system.
>>
>> HTH,
>>
>> Guido.
>>
>> On 10/10/13 10:43, Guido Medina wrote:
>>
>>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
>>> repo, we have in production for few years now with no issues, you just need
>>> to be sure your solr.war has the required jars in it, also your collection
>>> must have the extra jars needed by your app.
>>>
>>> We have been running it in Ubuntu Server 12.04 LTS for a long time, it
>>> is easy to have the jetty server with default repo package since it is easy
>>> to pass JVM parameters using /etc/default/jetty config file.
>>>
>>> HTH,
>>>
>>> Guido.
>>>
>>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>>
>>>> Do you get an error?
>>>>
>>>>
>>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>>
>>>> Hey folks,
>>>>> for some days i tried to get Solr 4.4.0 working as a webapp with Jetty
>>>>> 6.1
>>>>> from the Ubuntu repository installed with apt-get. First i tried the
>>>>> installation according the wiki http://wiki.apache.org/solr/**
>>>>> SolrJetty <http://wiki.apache.org/solr/SolrJetty>.
>>>>> Then
>>>>> i found this example
>>>>> http://www.kingstonlabs.com/**blog/how-to-install-solr-36-**
>>>>> on-ubuntu-1204/and<http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and>
>>>>> tried the Configuration according to the book pache Solr 4 Cookbook by
>>>>> Rafal Kuc.
>>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on Ubuntus
>>>>> jetty 6.1 :(
>>>>> Can somebody confirm that it's impossible or give me an advice how to
>>>>> run
>>>>> Solr 4.4.0 on Jetty 6.1?
>>>>> Regards
>>>>>
>>>>>
>>>
>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
My I forgot to mention where you need to copy the solr.war file:
/var/lib/jetty/webapps
Guido.
On 10/10/13 10:48, Guido Medina wrote:
> Here is the pertinent changes you need to pass to /etc/default/jetty:
>
> * JAVA_OPTIONS="-Djava.awt.headless=true -Dfile.encoding=UTF-8
> -server -Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
> -XX:+OptimizeStringConcat -XX:+UseStringCache"
> * JAVA_OPTIONS="-Dsolr.solr.home=$YOUR_SOLR_COLLECTION_HOME
> $JAVA_OPTIONS"
>
>
> Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to
> play with it. Adjust your solr collection home to whatever path is on
> your system.
>
> HTH,
>
> Guido.
>
> On 10/10/13 10:43, Guido Medina wrote:
>> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
>> repo, we have in production for few years now with no issues, you
>> just need to be sure your solr.war has the required jars in it, also
>> your collection must have the extra jars needed by your app.
>>
>> We have been running it in Ubuntu Server 12.04 LTS for a long time,
>> it is easy to have the jetty server with default repo package since
>> it is easy to pass JVM parameters using /etc/default/jetty config file.
>>
>> HTH,
>>
>> Guido.
>>
>> On 10/10/13 10:02, Furkan KAMACI wrote:
>>> Do you get an error?
>>>
>>>
>>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>>
>>>> Hey folks,
>>>> for some days i tried to get Solr 4.4.0 working as a webapp with
>>>> Jetty 6.1
>>>> from the Ubuntu repository installed with apt-get. First i tried the
>>>> installation according the wiki http://wiki.apache.org/solr/SolrJetty.
>>>> Then
>>>> i found this example
>>>> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and
>>>>
>>>> tried the Configuration according to the book pache Solr 4 Cookbook by
>>>> Rafal Kuc.
>>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on Ubuntus
>>>> jetty 6.1 :(
>>>> Can somebody confirm that it's impossible or give me an advice how
>>>> to run
>>>> Solr 4.4.0 on Jetty 6.1?
>>>> Regards
>>>>
>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
Here is the pertinent changes you need to pass to /etc/default/jetty:
* JAVA_OPTIONS="-Djava.awt.headless=true -Dfile.encoding=UTF-8 -server
-Xms8g -Xmx8g -XX:+UseG1GC -XX:MaxGCPauseMillis=50
-XX:+OptimizeStringConcat -XX:+UseStringCache"
* JAVA_OPTIONS="-Dsolr.solr.home=$YOUR_SOLR_COLLECTION_HOME $JAVA_OPTIONS"
Of course, the 1st JAVA_OPTIONS are our own tuning, you are free to play
with it. Adjust your solr collection home to whatever path is on your
system.
HTH,
Guido.
On 10/10/13 10:43, Guido Medina wrote:
> I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
> repo, we have in production for few years now with no issues, you just
> need to be sure your solr.war has the required jars in it, also your
> collection must have the extra jars needed by your app.
>
> We have been running it in Ubuntu Server 12.04 LTS for a long time, it
> is easy to have the jetty server with default repo package since it is
> easy to pass JVM parameters using /etc/default/jetty config file.
>
> HTH,
>
> Guido.
>
> On 10/10/13 10:02, Furkan KAMACI wrote:
>> Do you get an error?
>>
>>
>> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>>
>>> Hey folks,
>>> for some days i tried to get Solr 4.4.0 working as a webapp with
>>> Jetty 6.1
>>> from the Ubuntu repository installed with apt-get. First i tried the
>>> installation according the wiki http://wiki.apache.org/solr/SolrJetty.
>>> Then
>>> i found this example
>>> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and
>>>
>>> tried the Configuration according to the book pache Solr 4 Cookbook by
>>> Rafal Kuc.
>>> But it semmed to be impossible to run Solr 4.4.0 as webapp on Ubuntus
>>> jetty 6.1 :(
>>> Can somebody confirm that it's impossible or give me an advice how
>>> to run
>>> Solr 4.4.0 on Jetty 6.1?
>>> Regards
>>>
>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Guido Medina <gu...@temetra.com>.
I can confirm solr 3.x and 4.x runs fine with jetty 6.x from Ubuntu
repo, we have in production for few years now with no issues, you just
need to be sure your solr.war has the required jars in it, also your
collection must have the extra jars needed by your app.
We have been running it in Ubuntu Server 12.04 LTS for a long time, it
is easy to have the jetty server with default repo package since it is
easy to pass JVM parameters using /etc/default/jetty config file.
HTH,
Guido.
On 10/10/13 10:02, Furkan KAMACI wrote:
> Do you get an error?
>
>
> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>
>> Hey folks,
>> for some days i tried to get Solr 4.4.0 working as a webapp with Jetty 6.1
>> from the Ubuntu repository installed with apt-get. First i tried the
>> installation according the wiki http://wiki.apache.org/solr/SolrJetty.
>> Then
>> i found this example
>> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and
>> tried the Configuration according to the book pache Solr 4 Cookbook by
>> Rafal Kuc.
>> But it semmed to be impossible to run Solr 4.4.0 as webapp on Ubuntus
>> jetty 6.1 :(
>> Can somebody confirm that it's impossible or give me an advice how to run
>> Solr 4.4.0 on Jetty 6.1?
>> Regards
>>
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Tobias Kabbeck <to...@zeit.de>.
Am 10.10.13 11:02, schrieb Furkan KAMACI:
> Do you get an error?
As Webapp like in
http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/
i got a 404
Recipe from the cookbook produces some errors in the jetty log. i thinks the jetty.xml an the Java Class is different.
>
> 2013/10/10 Peter Schmidt <pe...@gmail.com>
>
>> Hey folks,
>> for some days i tried to get Solr 4.4.0 working as a webapp with Jetty 6.1
>> from the Ubuntu repository installed with apt-get. First i tried the
>> installation according the wiki http://wiki.apache.org/solr/SolrJetty.
>> Then
>> i found this example
>> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and
>> tried the Configuration according to the book pache Solr 4 Cookbook by
>> Rafal Kuc.
>> But it semmed to be impossible to run Solr 4.4.0 as webapp on Ubuntus
>> jetty 6.1 :(
>> Can somebody confirm that it's impossible or give me an advice how to run
>> Solr 4.4.0 on Jetty 6.1?
>> Regards
>>
--
Tobias Kabbeck
--------------------------
ZEIT ONLINE
Askanischer Platz 1
10963 Berlin
--------------------------
tobias.kabbeck@zeit.de
Tel: +49 (0)30 322 950 175
Mobil: +49 (0)160 96966428
--------------------------
www.zeit.de
DIE ZEIT jetzt am Kiosk.
www.zeit.de/diesewoche
----------------------------------------------------------------
ZEIT ONLINE - Durchschauen Sie jeden Tag.
www.zeit.de
___________________________________________
Zeitverlag Gerd Bucerius GmbH & Co. KG, 20079 Hamburg
Geschäftsführer: Dr. Rainer Esser
Handelsregister Hamburg HRA 91123
Amtsgericht Hamburg
http://www.zeit.de/
Re: Solr 4.4.0 on Ubuntu 10.04 with Jetty 6.1 from package Repository
Posted by Furkan KAMACI <fu...@gmail.com>.
Do you get an error?
2013/10/10 Peter Schmidt <pe...@gmail.com>
> Hey folks,
> for some days i tried to get Solr 4.4.0 working as a webapp with Jetty 6.1
> from the Ubuntu repository installed with apt-get. First i tried the
> installation according the wiki http://wiki.apache.org/solr/SolrJetty.
> Then
> i found this example
> http://www.kingstonlabs.com/blog/how-to-install-solr-36-on-ubuntu-1204/and
> tried the Configuration according to the book pache Solr 4 Cookbook by
> Rafal Kuc.
> But it semmed to be impossible to run Solr 4.4.0 as webapp on Ubuntus
> jetty 6.1 :(
> Can somebody confirm that it's impossible or give me an advice how to run
> Solr 4.4.0 on Jetty 6.1?
> Regards
>