Re: Membership log message questions

Thanks Bruce! I'll change the test to use crashDistributedSystem. On Mon, Mar 26, 2018 at 8:49 AM, Bruce Schuchardt wrote: > The problem is that the test is shutting down the cache in a high-priority > thread pool. When the ClusterDistributionManager tries to close its thread > pools it waits a

Re: Membership log message questions

The problem is that the test is shutting down the cache in a high-priority thread pool.  When the ClusterDistributionManager tries to close its thread pools it waits a while for their threads to exit, so the thread ends up waiting for itself to exit & that's not going to happen.  During that ti

Re: Membership log message questions

This is weird behavior Kirk.  It looks like vm0 was behaving very badly - I'll check into it. On 3/22/18 7:58 PM, Kirk Lund wrote: If anyone really wants to look at and run the test directly, it's *Bug41733DUnitTest* on develop. Alternatively, you could pull the branch GEODE-1279-rename-regre

Re: Membership log message questions

If anyone really wants to look at and run the test directly, it's *Bug41733DUnitTest* on develop. Alternatively, you could pull the branch GEODE-1279-rename-regressionTests from my fork (see *https://github.com/apache/geode/pull/1672 *) where I've renamed

Membership log message questions

I'm looking through logs from a DUnit test that takes longer to run than I think it should. It looks to me like membership is chewing up more time than it should, and I have questions about some membership log messages. Specifically, I'm worried about: 1) double-logging by vm1 when shutdown messag