Just caught this message. I'll fix ConnectToLocatorSSLDUnitTest and look for other tests that aren't tearing down gfsh properly.
-Kirk On Thu, Oct 27, 2016 at 12:49 PM, Jinmei Liao <jil...@pivotal.io> wrote: > Thanks Bruce. Looking at the ConnectToLocatorSSLDUnitTest, we did have a > gfsh there that's not properly closed. I will work with Kirk to close this. > Thanks! > > On Thu, Oct 27, 2016 at 11:46 AM, Bruce Schuchardt <bschucha...@pivotal.io > > > wrote: > > > I think the code is in Gfsh.notifyDisconnect(). I think the test that's > > polluting others is ConnectToLocatorSSLDUnitTest. I had a failure with > > this suspect string in a test that ran just after it. I added a thread > dump > > in the @After of that test and see that it's leaving one of these threads > > behind along with some Gfsh Launcher threads. > > > > > > Le 10/27/2016 à 10:54 AM, Kirk Lund a écrit : > > > >> Bruce, can you please point me at the JDK code you think is generating > the > >> fatal message? I looked in RMIConnector.java and can't find it in there. > >> > >> Maybe we can fix ordering of tearDown or something else in order to > "fix" > >> this message. > >> > >> Thanks, > >> Kirk > >> > >> > >> On Wed, Oct 26, 2016 at 5:00 PM, Dan Smith <dsm...@pivotal.io> wrote: > >> > >> Just looking at a couple of these bugs, these are fatal level errors. Do > >>> you know what is causing them or what affect this might have? > >>> > >>> [fatal 2016/09/29 12:12:03.891 PDT <JMX client heartbeat 3> tid=0x18d] > >>> (tid=397 msgId=39) No longer connected to cc6-co6.gemstone.com[27162]. > >>> > >>> -Dan > >>> > >>> On Wed, Oct 26, 2016 at 4:50 PM, Bruce Schuchardt < > >>> bschucha...@pivotal.io> > >>> wrote: > >>> > >>> We have 23 CI failure tickets concerning suspect strings from "JMX > client > >>>> heartbeat" threads. I think we should add this to > ExpectedStrings.java > >>>> > >>> and > >>> > >>>> close these tickets. The suspect strings are coming from > >>>> javax.management.remote.rmi.RMIConnector and I don't think there's > >>>> anything we can do about them. Most, if not all, are assigned to > >>>> > >>> security > >>> > >>>> or JMX components. > >>>> > >>>> > >>>> GEODE-1858 > >>>> GEODE-1955 > >>>> GEODE-1492 > >>>> GEODE-1539 > >>>> GEODE-1538 > >>>> GEODE-1773 > >>>> GEODE-1922 > >>>> GEODE-1482 > >>>> GEODE-1475 > >>>> GEODE-1480 > >>>> GEODE-1481 > >>>> GEODE-1826 > >>>> GEODE-1825 > >>>> GEODE-1820 > >>>> GEODE-1878 > >>>> GEODE-1879 > >>>> GEODE-1877 > >>>> GEODE-1875 > >>>> GEODE-1876 > >>>> GEODE-1499 > >>>> GEODE-1476 > >>>> GEODE-1869 > >>>> GEODE-1769 > >>>> > >>>> > >>>> > > > > > -- > Cheers > > Jinmei
