[
https://issues.apache.org/jira/browse/GEODE-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941361#comment-14941361
]
ASF subversion and git services commented on GEODE-378:
-------------------------------------------------------
Commit 9e4a94e06377094336cb31882b96e8aff2ebe8dd in incubator-geode's branch
refs/heads/develop from [~dschneider]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=9e4a94e ]
GEODE-378: use SynchronousQueue to prevent deadlock
The SynchronousQueueNoSpin class has been completely removed.
The JDK SynchronousQueue is now used in its place.
> Region initialization may hang
> ------------------------------
>
> Key: GEODE-378
> URL: https://issues.apache.org/jira/browse/GEODE-378
> Project: Geode
> Issue Type: Bug
> Components: core
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
>
> Region initialization may hang. The race condition that causes this is very
> rare.
> If it happens you will see a warning in the log like this:
> [warning 2015/06/19 21:51:56.051 PDT dataStoregemfire1_w1-gst-dev05_15990
> <vm_1_thr_17_dataStore1_w1-gst-dev05_15990> tid=0x1a] 15 seconds have elapsed
> while waiting for replies: <CreateRegionProcessor$CreateRegionReplyProcessor
> 5 waiting for 1 replies from
> [w1-gst-dev05(dataStoregemfire4_w1-gst-dev05_15323:15323)<v10>:17784]> on ...
> The hang is caused by the member that this message is waiting for a reply
> from. That member received this message but, due to the race condition, did
> not process it. It never will. Thread dumps of that member show that it is
> not stuck working on this message. This bug caused that member to drop the
> message when it was scheduling it for execution in a thread pool.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
