[
https://issues.apache.org/jira/browse/GEODE-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076447#comment-17076447
]
ASF subversion and git services commented on GEODE-7098:
--------------------------------------------------------
Commit abd0f54dd280b64473a4ef36149d31de4a74da1d in geode's branch
refs/heads/develop from mhansonp
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=abd0f54 ]
GEODE-7098: Tomcat8SessionsClientServerDUnitTest Tests were getting bind
failures (#4903)
* GEODE-7098: Tests were getting bind failures using
SocketUtils.getAvailableTCPPort
- Moved tests to use AvailablePortHelper class
- Added Sanity check to setup
- Rename testSanity call to basicConnectivityCheck
- Inline testSanity
Co-authored-by: Mark Hanson <[email protected]>
> Tomcat8SessionsClientServerDUnitTest fails with ConnectException
> ----------------------------------------------------------------
>
> Key: GEODE-7098
> URL: https://issues.apache.org/jira/browse/GEODE-7098
> Project: Geode
> Issue Type: Bug
> Reporter: Benjamin P Ross
> Assignee: Mark Hanson
> Priority: Major
> Labels: flaky
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> We've seen Tomcat8SessionsClientServerDUnitTest.testExtraSessionsNotCreated
> fail with
> a ConnectException
> org.apache.geode.modules.session.Tomcat8SessionsClientServerDUnitTest >
> testExtraSessionsNotCreated FAILED
> java.net.ConnectException: Connection refused (Connection refused)
> Caused by:
> java.net.ConnectException: Connection refused (Connection refused)
> This could be an environmental error, but if a pattern develops it could be
> due to a flaky test.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)