xiaojian zhou created GEODE-375:
-----------------------------------
Summary: A lot of suspect string in HAStartupAndFailoverDUnitTest
Key: GEODE-375
URL: https://issues.apache.org/jira/browse/GEODE-375
Project: Geode
Issue Type: Bug
Components: client/server
Environment: develop
Reporter: xiaojian zhou
Assignee: Anilkumar Gingade
Priority: Critical
Run the dunit test: HAStartupAndFailoverDUnitTest, it failed with following
suspicous strings:
:gemfire-core:distributedTest
com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest
>
testCacheClientUpdaterInitiatesFailoverOnBothPrimaryAndSecondaryFailureWithServerMonitors
FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use DistributedTestCase.addExpectedException to ignore.
-----------------------------------------------------------------------
Found suspect string in log4j at line 3862
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3901
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3929
java.net.ConnectException: Connection refused: connect
com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest
> testExceptionWhileMakingPrimary FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use DistributedTestCase.addExpectedException to ignore.
-----------------------------------------------------------------------
Found suspect string in log4j at line 3051
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3117
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3183
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3211
java.net.ConnectException: Connection refused: connect
com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest
> testCacheClientUpdatersInitiatesFailoverOnPrimaryFailure FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use DistributedTestCase.addExpectedException to ignore.
-----------------------------------------------------------------------
Found suspect string in log4j at line 3101
java.net.ConnectException: Connection refused: connect
com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest
> testPrimaryShouldBeNullAndEPListShouldBeEmptyWhenAllServersAreDead FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use DistributedTestCase.addExpectedException to ignore.
-----------------------------------------------------------------------
Found suspect string in log4j at line 3109
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3135
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3165
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3194
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3220
java.net.ConnectException: Connection refused: connect
com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest
> testTwoPrimaryFailedOneAfterTheAnother FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use DistributedTestCase.addExpectedException to ignore.
-----------------------------------------------------------------------
Found suspect string in log4j at line 3101
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3137
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3165
java.net.ConnectException: Connection refused: connect
com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest >
testCacheClientUpdaterInitiatesFailoverOnSecondaryFailure FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use DistributedTestCase.addExpectedException to ignore.
-----------------------------------------------------------------------
Found suspect string in log4j at line 3097
java.net.ConnectException: Connection refused: connect
com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest
> testCacheClientUpdaterInitiatesFailoverOnBothPrimaryAndSecondaryFailure FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use DistributedTestCase.addExpectedException to ignore.
-----------------------------------------------------------------------
Found suspect string in log4j at line 3105
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3141
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3169
java.net.ConnectException: Connection refused: connect
com.gemstone.gemfire.internal.cache.tier.sockets.HAStartupAndFailoverDUnitTest
> testPrimaryFailover FAILED
java.lang.AssertionError: Suspicious strings were written to the log during
this run.
Fix the strings or use DistributedTestCase.addExpectedException to ignore.
-----------------------------------------------------------------------
Found suspect string in log4j at line 3103
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3147
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3175
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3201
java.net.ConnectException: Connection refused: connect
-----------------------------------------------------------------------
Found suspect string in log4j at line 3231
java.net.ConnectException: Connection refused: connect
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
