[ https://issues.apache.org/jira/browse/GEODE-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Hanson resolved GEODE-3733. -------------------------------- Resolution: Fixed Fix Version/s: 1.7.0 Marked as not flaky after it passed a bunch of test passes and some discussions with other developers that led me to believe this may not be a valid bug anymore. > CacheMaxConnectionJUnitTest marked as flaky > ------------------------------------------- > > Key: GEODE-3733 > URL: https://issues.apache.org/jira/browse/GEODE-3733 > Project: Geode > Issue Type: Bug > Components: client/server > Reporter: Hitesh Khamesra > Assignee: Mark Hanson > Priority: Major > Labels: flaky, pull-request-available > Fix For: 1.7.0 > > Time Spent: 50m > Remaining Estimate: 0h > > org.apache.geode.internal.protocol.acceptance.CacheMaxConnectionJUnitTest > > testNewProtocolRespectsMaxConnectionLimit_notSelector FAILED > java.lang.AssertionError: expected null, but > was:<java.net.SocketException: Broken pipe (Write failed)> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotNull(Assert.java:755) > at org.junit.Assert.assertNull(Assert.java:737) > at org.junit.Assert.assertNull(Assert.java:747) > at > org.apache.geode.internal.protocol.acceptance.CacheMaxConnectionJUnitTest.validateSocketCreationAndDestruction(CacheMaxConnectionJUnitTest.java:206) > at > org.apache.geode.internal.protocol.acceptance.CacheMaxConnectionJUnitTest.testNewProtocolRespectsMaxConnectionLimit(CacheMaxConnectionJUnitTest.java:154) > at > org.apache.geode.internal.protocol.acceptance.CacheMaxConnectionJUnitTest.testNewProtocolRespectsMaxConnectionLimit_notSelector(CacheMaxConnectionJUnitTest.java:123) -- This message was sent by Atlassian JIRA (v7.6.3#76005)