geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darrel Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GEODE-358) ClientServerFunctionExecutionDUnitTest.testOnServerFailoverWithTwoServerDownHA fails intermittently with suspect string
Date Tue, 22 Sep 2015 21:09:04 GMT
Darrel Schneider created GEODE-358:
--------------------------------------

             Summary: ClientServerFunctionExecutionDUnitTest.testOnServerFailoverWithTwoServerDownHA
fails intermittently with suspect string
                 Key: GEODE-358
                 URL: https://issues.apache.org/jira/browse/GEODE-358
             Project: Geode
          Issue Type: Bug
          Components: client/server
            Reporter: Darrel Schneider
            Assignee: Anilkumar Gingade
            Priority: Minor


Seen on a private build using git rev: 4708d4e182f89c6a391fcad8bac854f929717685

{code}
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 3063

java.net.SocketException: Connection reset by peer
{code}

The logs containing the suspect string:
{code}
[vm_0][info 2015/09/21 00:24:53.238 PDT <RMI TCP Connection(30)-10.118.33.102> tid=0x3988]
Bridge server on port 26,030 is shutting down.
[vm_0]
[vm_3][info 2015/09/21 00:24:53.240 PDT <Cache Client Updater Thread  on doomtwo(989)<v1255>:4546
port 26030> tid=0x1268] Cache client updater for Queue on endpoint doomtwo.gemstone.com:26030
exiting. Scheduling recovery.
[vm_3]
[vm_3][warn 2015/09/21 00:24:53.240 PDT <poolTimer-PRClientServerTestBaseWithoutRegion-2>
tid=0x1261] Pool unexpected closed socket on server connection=SubscriptionConnectionImpl[doomtwo.gemstone.com:26030:closed]).
Server unreachable: could not connect after 1 attempts
[vm_3]
[vm_3][warn 2015/09/21 00:24:53.240 PDT <queueTimer-PRClientServerTestBaseWithoutRegion>
tid=0x1269] Could not connect to: doomtwo.gemstone.com:26030
[vm_3]java.net.SocketException: Connection reset by peer
[vm_3]	at java.net.PlainSocketImpl.socketConnect(Native Method)
[vm_3]	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
[vm_3]	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
[vm_3]	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
[vm_3]	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
[vm_3]	at java.net.Socket.connect(Socket.java:589)
[vm_3]	at com.gemstone.gemfire.internal.SocketUtils.connect(SocketUtils.java:85)
[vm_3]	at com.gemstone.gemfire.internal.SocketUtils.connect(SocketUtils.java:57)
[vm_3]	at com.gemstone.gemfire.internal.SocketCreator.connect(SocketCreator.java:1013)
[vm_3]	at com.gemstone.gemfire.internal.SocketCreator.connect(SocketCreator.java:948)
[vm_3]	at com.gemstone.gemfire.internal.SocketCreator.connectForClient(SocketCreator.java:917)
[vm_3]	at com.gemstone.gemfire.cache.client.internal.ConnectionImpl.connect(ConnectionImpl.java:113)
[vm_3]	at com.gemstone.gemfire.cache.client.internal.ConnectionFactoryImpl.createClientToServerConnection(ConnectionFactoryImpl.java:117)
[vm_3]	at com.gemstone.gemfire.cache.client.internal.QueueManagerImpl.createNewPrimary(QueueManagerImpl.java:785)
[vm_3]	at com.gemstone.gemfire.cache.client.internal.QueueManagerImpl.recoverPrimary(QueueManagerImpl.java:903)
[vm_3]	at com.gemstone.gemfire.cache.client.internal.QueueManagerImpl$RedundancySatisfierTask.run2(QueueManagerImpl.java:1428)
[vm_3]	at com.gemstone.gemfire.cache.client.internal.PoolImpl$PoolTask.run(PoolImpl.java:1250)
[vm_3]	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[vm_3]	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[vm_3]	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
[vm_3]	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[vm_3]	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[vm_3]	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[vm_3]	at java.lang.Thread.run(Thread.java:745)
{code}




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message