You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2015/09/22 20:48:05 UTC
[jira] [Reopened] (GEODE-108)
HAInterestPart2DUnitTest.testInterestRecoveryFailure failed with suspect
string
[ https://issues.apache.org/jira/browse/GEODE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darrel Schneider reopened GEODE-108:
------------------------------------
This was seen on git rev: 4708d4e182f89c6a391fcad8bac854f929717685
for test: HAInterestPart2DUnitTest.testInterestRecoveryFailure
{code}
Error Message
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 3936
java.net.SocketException: Connection reset by peer
{code}
Here is the part of the log that had the suspect:
{code}
[vm_0][info 2015/09/20 20:21:54.815 PDT <RMI TCP Connection(15)-10.118.33.94> tid=0x947] Bridge server on port 28,989 is shutting down.
[vm_0]
[warn 2015/09/20 20:21:54.815 PDT <poolTimer-HAInterestBaseTestPool-2> tid=0x5b6] Could not connect to: cc4-rh6.gemstone.com:28989
java.net.SocketException: Connection reset by peer
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at com.gemstone.gemfire.internal.SocketUtils.connect(SocketUtils.java:85)
at com.gemstone.gemfire.internal.SocketUtils.connect(SocketUtils.java:57)
at com.gemstone.gemfire.internal.SocketCreator.connect(SocketCreator.java:1013)
at com.gemstone.gemfire.internal.SocketCreator.connect(SocketCreator.java:948)
at com.gemstone.gemfire.internal.SocketCreator.connectForClient(SocketCreator.java:917)
at com.gemstone.gemfire.cache.client.internal.ConnectionImpl.connect(ConnectionImpl.java:113)
at com.gemstone.gemfire.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:117)
at com.gemstone.gemfire.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:233)
at com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerImpl.prefillConnection(ConnectionManagerImpl.java:795)
at com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerImpl.prefill(ConnectionManagerImpl.java:738)
at com.gemstone.gemfire.cache.client.internal.pooling.ConnectionManagerImpl$PrefillConnectionsTask.run2(ConnectionManagerImpl.java:889)
at com.gemstone.gemfire.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1250)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
[info 2015/09/20 20:21:54.816 PDT <Cache Client Updater Thread on cc4-rh6(27426)<v197>:17599 port 28989> tid=0x5bc] Primary subscription endpoint cc4-rh6.gemstone.com:28989 crashed. Scheduling recovery.
[info 2015/09/20 20:21:54.816 PDT <queueTimer-HAInterestBaseTestPool> tid=0x5bd] SubscriptionManager redundancy satisfier - primary endpoint has been lost. Attempting to recover.
{code}
> HAInterestPart2DUnitTest.testInterestRecoveryFailure failed with suspect string
> -------------------------------------------------------------------------------
>
> Key: GEODE-108
> URL: https://issues.apache.org/jira/browse/GEODE-108
> Project: Geode
> Issue Type: Bug
> Reporter: Kirk Lund
> Assignee: Kirk Lund
> Fix For: 1.0.0-incubating
>
>
> {code}
> com.gemstone.gemfire.internal.cache.tier.sockets.HAInterestPart2DUnitTest > testInterestRecoveryFailure 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 3864
> java.net.SocketException: Connection reset by peer
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)