Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D503F2004A1 for ; Thu, 24 Aug 2017 18:57:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D35E816B2A2; Thu, 24 Aug 2017 16:57:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4C60A16B29F for ; Thu, 24 Aug 2017 18:57:11 +0200 (CEST) Received: (qmail 32492 invoked by uid 500); 24 Aug 2017 16:57:10 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 32478 invoked by uid 99); 24 Aug 2017 16:57:10 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Aug 2017 16:57:10 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D8467C0334 for ; Thu, 24 Aug 2017 16:57:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id xXQ36GeRdmno for ; Thu, 24 Aug 2017 16:57:09 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 84AE95FBBA for ; Thu, 24 Aug 2017 16:57:08 +0000 (UTC) Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37]) by mwork.nabble.com (Postfix) with ESMTP id DE5695F277271 for ; Thu, 24 Aug 2017 09:57:07 -0700 (MST) Date: Thu, 24 Aug 2017 09:57:07 -0700 (MST) From: "slava.koptilin" To: user@ignite.apache.org Message-ID: <1503593827904-16406.post@n6.nabble.com> In-Reply-To: <1503511922425-16383.post@n6.nabble.com> References: <1503339330689-16346.post@n6.nabble.com> <1503406348353-16364.post@n6.nabble.com> <1503511922425-16383.post@n6.nabble.com> Subject: Re: ignite.active(true) blocking forever MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Thu, 24 Aug 2017 16:57:12 -0000 Hi, I don't think there is a way to properly recover application/server or any other service once out of memory error arises. Just trying to send a simple notification may lead to another attempt to allocate memory and therefore new OOME must be thrown. So, the best way to treat OOME is to treat it as unrecoverable error. Thanks! -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-active-true-blocking-forever-tp16346p16406.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.