Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5CA2218EA0 for ; Fri, 25 Sep 2015 14:40:04 +0000 (UTC) Received: (qmail 74620 invoked by uid 500); 25 Sep 2015 14:40:04 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 74517 invoked by uid 500); 25 Sep 2015 14:40:04 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 74426 invoked by uid 99); 25 Sep 2015 14:40:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Sep 2015 14:40:04 +0000 Date: Fri, 25 Sep 2015 14:40:04 +0000 (UTC) From: "James Bench (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-1551) IgniteCache.put hangs indefinatly MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 James Bench created IGNITE-1551: ----------------------------------- Summary: IgniteCache.put hangs indefinatly Key: IGNITE-1551 URL: https://issues.apache.org/jira/browse/IGNITE-1551 Project: Ignite Issue Type: Bug Components: cache Environment: Ubuntu 14.04 java version "1.8.0_51" Java(TM) SE Runtime Environment (build 1.8.0_51-b16) Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode) Tomcat 7 Reporter: James Bench We have a process that pulls jobs from a queue and puts associated assets into a cache using IgniteCache.put. The object we put into the cache is an object holding a map of Enums and byte arrays. {code} private Map assets = new EnumMap<>(AssetTypeEnum.class); {code} We are using a UUID as the key. The byte arrays can become quite large - the batch it was processing when the issue occurred were up to 30mb in size. The thread got stuck in {code}IgniteCache.put{code} and remained stuck for a few hours until we restarted Tomcat. I took a memory Snapshot using YourKit while the application was frozen (attached) which shows the thread {{taskExecutorBean-3}} waiting in sun.misc.Unsafe.park. It has spent 100% of the time I profiled here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)