Here is the stack trace. A lot of information is lost due to the way that
we are starting members in our benchmark, but I will see what I can get
from the logs and give an update.
org.apache.geode.benchmark.tests.PartitionedPutBenchmarkTest >
benchmarkRunsSuccessfully() FAILED
java.util.concurrent.CompletionException: java.lang.RuntimeException:
java.rmi.ServerError: Error occurred in server thread; nested exception is:
java.lang.NoClassDefFoundError:
org/eclipse/jetty/webapp/WebAppContext
Caused by:
java.lang.RuntimeException: java.rmi.ServerError: Error occurred in
server thread; nested exception is:
java.lang.NoClassDefFoundError:
org/eclipse/jetty/webapp/WebAppContext
Caused by:
java.rmi.ServerError: Error occurred in server thread; nested
exception is:
java.lang.NoClassDefFoundError:
org/eclipse/jetty/webapp/WebAppContext
Caused by:
java.lang.NoClassDefFoundError:
org/eclipse/jetty/webapp/WebAppContext
Caused by:
java.lang.ClassNotFoundException:
org.eclipse.jetty.webapp.WebAppContext
On Tue, Mar 5, 2019 at 11:24 AM Anthony Baker <aba...@pivotal.io> wrote:
> Do you have a full stack trace? I’m curious where we are using this…I
> assume it’s on the client?
>
> > On Mar 5, 2019, at 11:08 AM, Helena Bales <hba...@pivotal.io> wrote:
> >
> > It appears the jetty-webapp dependency is now required, and not optional.
> > Was there a reason that it was originally marked as optional in the
> > geode-core build.gradle? Should it still be optional, and if so,
> something
> > is broken? This optional dependency in the POM is causing downstream
> > projects like benchmarks to fail tests due to ClassNotFound exceptions on
> > WebAppContext. Removing the optional flag fixed benchmark tests.
> >
> > ~Helena Bales
>
>
