[GEODE-7753] CI Failure: Tomcat9CachingClientServerTest. multipleClientsCanMaintainOwnSessions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.12.0
• Assignee: Ernest Burghardt
• Reporter: Benjamin P Ross
• Created: 30/Jan/20 20:06
• Updated: 30/Mar/20 23:32
• Resolved: 31/Jan/20 01:06

Description

We saw a failure in CI for this test: 

org.apache.geode.session.tests.Tomcat9CachingClientServerTest > multipleClientsCanMaintainOwnSessions FAILED
    org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.session.tests.CargoTestBase expected:<"[Foo55]"> but was:<"[]"> within 300 seconds.

        Caused by:
        org.junit.ComparisonFailure: expected:<"[Foo55]"> but was:<"[]">

    java.lang.NullPointerException

org.apache.geode.session.tests.Tomcat6CachingClientServerTest > multipleClientsCanMaintainOwnSessions FAILED
    org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.session.tests.CargoTestBase expected:<"[Foo55]"> but was:<"[]"> within 300 seconds.

        Caused by:
        org.junit.ComparisonFailure: expected:<"[Foo55]"> but was:<"[]">

    java.lang.NullPointerException

org.apache.geode.session.tests.Tomcat7CachingClientServerTest > multipleClientsCanMaintainOwnSessions FAILED
    org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.session.tests.CargoTestBase expected:<"[Foo55]"> but was:<"[]"> within 300 seconds.

        Caused by:
        org.junit.ComparisonFailure: expected:<"[Foo55]"> but was:<"[]">

    org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.geode.session.tests.CargoTestBase expected:<"[Foo55]"> but was:<"[]"> within 300 seconds.

        Caused by:
        org.junit.ComparisonFailure: expected:<"[Foo55]"> but was:<"[]">

    java.lang.NullPointerException

    java.lang.NullPointerException

 

It's possible that this issue could show up in Tomcat 7,8, and 9 tests.