You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/14 00:41:00 UTC
[jira] [Commented] (GEODE-6377) Unit test hang:
ParallelGatewaySenderOperationsOffHeapDUnitTest
testDestroyParallelGatewaySenderExceptionScenario
[ https://issues.apache.org/jira/browse/GEODE-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767742#comment-16767742 ]
ASF subversion and git services commented on GEODE-6377:
--------------------------------------------------------
Commit 6176b1b16a3a09cb6b82c96ccb31821b88a47573 in geode's branch refs/heads/feature/GEODE-6389 from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=6176b1b ]
GEODE-6389 CI Failure: ConcurrentWANPropagation_1_DUnitTest.testReplicatedSerialPropagation
I found a place where we were releasing pooled buffers twice. The place
to release the buffer is in asyncClose but we were also doing it just
after calling that method in the run() method if the connection wasn't
thread-owned. Both GEODE-6389 and GEODE-6377 were using
conserve-sockets=true so I think this is the source of the problem.
The GEODE-6389 failure, in particular, could only have come from
improper use of the buffer pool because it occured in a MessageStreamer
and they don't involve multithreaded use of a buffer.
> Unit test hang: ParallelGatewaySenderOperationsOffHeapDUnitTest testDestroyParallelGatewaySenderExceptionScenario
> -----------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-6377
> URL: https://issues.apache.org/jira/browse/GEODE-6377
> Project: Geode
> Issue Type: Bug
> Components: serialization
> Reporter: Bruce Schuchardt
> Assignee: Bruce Schuchardt
> Priority: Major
>
> This test hung in distributed test run #376
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/376]
> Test output showed this exception
> {noformat}
> [vm5] [fatal 2019/02/06 17:16:51.394 UTC <P2P message reader for 172.17.0.2(655)<v1>:41005 shared unordered uid=65 port=58010> tid=0x407] Error deserializing message
> [vm5] org.apache.geode.SerializationException: Could not create an instance of org.apache.geode.internal.cache.UpdateAttributesProcessor$ProfileReplyMessage .
> [vm5] at org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2508)
> [vm5] at org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:994)
> [vm5] at org.apache.geode.internal.InternalDataSerializer.readDSFID(InternalDataSerializer.java:2632)
> [vm5] at org.apache.geode.internal.InternalDataSerializer.readDSFID(InternalDataSerializer.java:2646)
> [vm5] at org.apache.geode.internal.tcp.Connection.readMessage(Connection.java:3127)
> [vm5] at org.apache.geode.internal.tcp.Connection.processInputBuffer(Connection.java:2941)
> [vm5] at org.apache.geode.internal.tcp.Connection.readMessages(Connection.java:1730)
> [vm5] at org.apache.geode.internal.tcp.Connection.run(Connection.java:1564)
> [vm5] at java.lang.Thread.run(Thread.java:748)
> [vm5] Caused by: java.nio.BufferUnderflowException
> [vm5] at java.nio.Buffer.nextGetIndex(Buffer.java:500)
> [vm5] at java.nio.DirectByteBuffer.get(DirectByteBuffer.java:249)
> [vm5] at org.apache.geode.internal.tcp.ByteBufferInputStream$ByteBufferByteSource.get(ByteBufferInputStream.java:206)
> [vm5] at org.apache.geode.internal.tcp.ByteBufferInputStream.readByte(ByteBufferInputStream.java:892)
> [vm5] at org.apache.geode.distributed.internal.ReplyMessage.fromData(ReplyMessage.java:302)
> [vm5] at org.apache.geode.internal.cache.UpdateAttributesProcessor$ProfileReplyMessage.fromData(UpdateAttributesProcessor.
> {noformat}
>
> Followed later by this complaint:
> {noformat}
> [vm5] [warn 2019/02/06 17:17:06.391 UTC <RMI TCP Connection(1)-172.17.0.2> tid=0x20] 15 seconds have elapsed while waiting for replies: <UpdateAttributesProcessor$UpdateAttributesReplyProcessor 13358 waiting for 1 replies from [172.17.0.2(655)<v1>:41005]> on 172.17.0.2(758)<v2>:41006 whose current membership list is: [[172.17.0.2(861)<v3>:41007, 172.17.0.2(758)<v2>:41006, 172.17.0.2(243:locator)<ec><v0>:41001, 172.17.0.2(964)<v4>:41008, 172.17.0.2(655)<v1>:41005]]
> {noformat}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)