Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3189E1962D for ; Mon, 28 Mar 2016 00:32:23 +0000 (UTC) Received: (qmail 7592 invoked by uid 500); 28 Mar 2016 00:32:22 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 7543 invoked by uid 500); 28 Mar 2016 00:32:22 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 7532 invoked by uid 99); 28 Mar 2016 00:32:22 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Mar 2016 00:32:22 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0871A1A10EA for ; Mon, 28 Mar 2016 00:32:22 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.314 X-Spam-Level: ** X-Spam-Status: No, score=2.314 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_NONE=-0.0001, URI_HEX=1.313, URI_TRY_3LD=0.001] autolearn=disabled Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id YedmocZXRD4o for ; Mon, 28 Mar 2016 00:32:19 +0000 (UTC) Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTP id 293AD5F23B for ; Mon, 28 Mar 2016 00:32:19 +0000 (UTC) Received: from mjoe.nabble.com (unknown [162.253.133.57]) by mwork.nabble.com (Postfix) with ESMTP id 7D5C31F706583 for ; Sun, 27 Mar 2016 17:20:00 -0700 (PDT) Date: Sun, 27 Mar 2016 17:02:15 -0700 (PDT) From: artnaseef To: users@activemq.apache.org Message-ID: <1459123335085-4709974.post@n4.nabble.com> In-Reply-To: <1459061548754-4709973.post@n4.nabble.com> References: <1458984442271-4709963.post@n4.nabble.com> <1459061548754-4709973.post@n4.nabble.com> Subject: Re: ActiveMQ hangs and i don't understand why MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit OutOfMemory most commonly occurs with slow consumption. The broker can run out of memory if messages are produced to it too quickly and consumers don't keep up. It will also run out of memory if massive transactions are used and not committed nor rolled back before the broker's memory is exhausted. If this is the cause of problems, changing the JDK used won't eliminate it. A good next diagnostic step is to watch Queues, and Topic subscriptions, for slow consumption and see if that's related to the problem. -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-hangs-and-i-don-t-understand-why-tp4709963p4709974.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.