I like that approach. I'll raise a ticket to fail gracefully if the service
cannot be started due to missing dependencies.
--Jens
On Tue, Mar 5, 2019 at 2:59 PM Jacob Barrett wrote:
>
>
> > On Mar 5, 2019, at 1:52 PM, Jens Deppe wrote:
> >
> > How are building the code that's running here? Is
> On Mar 5, 2019, at 1:52 PM, Jens Deppe wrote:
>
> How are building the code that's running here? Is it a Maven or Gradle
> project and, if so, what dependencies are you declaring?
Project geode-benchmarks is a Gradle project that depends on geode-core. Since
the jetty-webapp dependency is
Ok, so from looking at the logs, here is what I've found:
locator-0: fatal - membership service failure due to loss of quorum
server-1: fatal - membership service failure, ForcedDisconnectException:
member isn't responding to heartbeats
server-2: fatal - locator declares that a network partition ha
How are building the code that's running here? Is it a Maven or Gradle
project and, if so, what dependencies are you declaring?
--Jens
On Tue, Mar 5, 2019 at 1:35 PM Jinmei Liao wrote:
> we've made a change to create an HttpService object when a non-client cache
> is created. This will allow us
we've made a change to create an HttpService object when a non-client cache
is created. This will allow us to deploy various web apps to this
HttpService at different phases of cache initialization. So now jetty is
not an optional package anymore.
On Tue, Mar 5, 2019 at 12:49 PM Helena Bales wrot
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.concur
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 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 th
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
