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 <peter.schmidt0...@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 <billnb...@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." <dsmi...@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.med...@temetra.com> wrote:
2. Java version: There are huges performance winning between Java 5, 6
and 7; we use Oracle JDK 7u40.