You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Geode Integration (Jira)" <ji...@apache.org> on 2022/06/08 03:30:00 UTC

[jira] [Commented] (GEODE-7098) Tomcat8SessionsClientServerDUnitTest fails with ConnectException

    [ https://issues.apache.org/jira/browse/GEODE-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551377#comment-17551377 ] 

Geode Integration commented on GEODE-7098:
------------------------------------------

Seen on support/1.12 in [distributed-test-openjdk11 #77|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-12-main/jobs/distributed-test-openjdk11/builds/77] ... see [test results|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.10-build.0408/test-results/distributedTest/1654654688/] or download [artifacts|http://files.apachegeode-ci.info/builds/apache-support-1-12-main/1.12.10-build.0408/test-artifacts/1654654688/distributedtestfiles-openjdk11-1.12.10-build.0408.tgz].

> Tomcat8SessionsClientServerDUnitTest fails with ConnectException
> ----------------------------------------------------------------
>
>                 Key: GEODE-7098
>                 URL: https://issues.apache.org/jira/browse/GEODE-7098
>             Project: Geode
>          Issue Type: Bug
>    Affects Versions: 1.11.0
>            Reporter: Benjamin P Ross
>            Assignee: Mark Hanson
>            Priority: Major
>              Labels: flaky
>             Fix For: 1.13.0
>
>          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.20.7#820007)