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/07/30 00:35:04 UTC
[jira] [Resolved] (GEODE-169)
Bug36853EventsExpiryDUnitTest.testEventsExpiryBug fails because of
unexpected IOException
[ https://issues.apache.org/jira/browse/GEODE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Darrel Schneider resolved GEODE-169.
------------------------------------
Resolution: Fixed
> Bug36853EventsExpiryDUnitTest.testEventsExpiryBug fails because of unexpected IOException
> -----------------------------------------------------------------------------------------
>
> Key: GEODE-169
> URL: https://issues.apache.org/jira/browse/GEODE-169
> Project: Geode
> Issue Type: Bug
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Minor
>
> Bug36853EventsExpiryDUnitTest.testEventsExpiryBug fails intermittently like so:
> 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 647
> [warn 2015/07/28 04:32:47.018 PDT <ServerConnection on port 25082 Thread 1> tid=0x4cf1] Server connection from [identity(cc1-co(27992:loner):34963:63876fd4,connection=1; port=34963]: Unexpected IOException:
> The full stack of this exception is:[vm_0][warn 2015/07/28 04:32:47.018 PDT <ServerConnection on port 25082 Thread 1> tid=0x4cf1] Server connection from [identity(cc1-co(27992:loner):34963:63876fd4,connection=1; port=34963]: Unexpected IOException:
> [vm_0]java.net.SocketException: Connection reset
> [vm_0] at java.net.SocketInputStream.read(SocketInputStream.java:196)
> [vm_0] at java.net.SocketInputStream.read(SocketInputStream.java:122)
> [vm_0] at com.gemstone.gemfire.internal.cache.tier.sockets.Message.fetchHeader(Message.java:699)
> [vm_0] at com.gemstone.gemfire.internal.cache.tier.sockets.Message.readHeaderAndPayload(Message.java:723)
> [vm_0] at com.gemstone.gemfire.internal.cache.tier.sockets.Message.read(Message.java:666)
> [vm_0] at com.gemstone.gemfire.internal.cache.tier.sockets.Message.recv(Message.java:1156)
> [vm_0] at com.gemstone.gemfire.internal.cache.tier.sockets.Message.recv(Message.java:1170)
> [vm_0] at com.gemstone.gemfire.internal.cache.tier.sockets.BaseCommand.readRequest(BaseCommand.java:939)
> [vm_0] at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:741)
> [vm_0] at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
> [vm_0] at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1159)
> [vm_0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [vm_0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [vm_0] at com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:580)
> [vm_0] at java.lang.Thread.run(Thread.java:745)
> The test will allow a "Connection reset" but in this case only sees: "Unexpected IOException".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)