From users-return-49643-archive-asf-public=cust-asf.ponee.io@activemq.apache.org Tue Mar 13 11:39:52 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 0D23118064F for ; Tue, 13 Mar 2018 11:39:51 +0100 (CET) Received: (qmail 22618 invoked by uid 500); 13 Mar 2018 10:39:50 -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 22570 invoked by uid 99); 13 Mar 2018 10:39:49 -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; Tue, 13 Mar 2018 10:39:49 +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 43AE71A4FC0 for ; Tue, 13 Mar 2018 10:39:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URI_HEX=1.313, URI_TRY_3LD=1.999] autolearn=disabled Received: from mx1-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 UFYtTmsjQVhs for ; Tue, 13 Mar 2018 10:39:47 +0000 (UTC) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 4AAD95F178 for ; Tue, 13 Mar 2018 10:39:47 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 3377F800 for ; Tue, 13 Mar 2018 10:39:46 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 2BE2E5D6A3 for ; Tue, 13 Mar 2018 10:39:46 +0000 (UTC) Received: from zmail21.collab.prod.int.phx2.redhat.com (zmail21.collab.prod.int.phx2.redhat.com [10.5.83.24]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id 265524CA98 for ; Tue, 13 Mar 2018 10:39:46 +0000 (UTC) Date: Tue, 13 Mar 2018 06:39:46 -0400 (EDT) From: Miroslav Novak To: users@activemq.apache.org Message-ID: <1185369579.10632376.1520937586066.JavaMail.zimbra@redhat.com> In-Reply-To: <1520932249654-0.post@n4.nabble.com> References: <1520932249654-0.post@n4.nabble.com> Subject: Re: Artemis: AMQ119014: Timed out after waiting 30,000 ms for response when sending packet 71 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.40.5.160, 10.4.195.11] Thread-Topic: Artemis: AMQ119014: Timed out after waiting 30,000 ms for response when sending packet 71 Thread-Index: ys6EaeL5+xKJpTl1VkYZ3Jjo0pIMBg== X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Tue, 13 Mar 2018 10:39:46 +0000 (UTC) Hi, did you manage to make thread dump of broker? I suspect that broker will send response packet for this message after all messages from queue are removed. This might take more than 30s if there are lots of messages. Thread dump would show what the broker is doing and if it's really so. Thanks, Mirek ----- Original Message ----- > From: "vishal3007" > To: users@activemq.apache.org > Sent: Tuesday, March 13, 2018 10:10:49 AM > Subject: Artemis: AMQ119014: Timed out after waiting 30,000 ms for response when sending packet 71 > > I am trying to remove the messages from 1 or my queue and occasionally I am > getting the timeout error: > > ERROR: global.search.data.load - AMQ119014: Timed out after waiting 30,000 > ms for response when sending packet 71 > javax.jms.JMSException: AMQ119014: Timed out after waiting 30,000 ms for > response when sending packet 71 > at > org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:399) > at config.xml > > org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:318) > at > org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQSessionContext.sendFullMessage(ActiveMQSessionContext.java:418) > at > org.apache.activemq.artemis.core.client.impl.ClientProducerImpl.sendRegularMessage(ClientProducerImpl.java:287) > at > org.apache.activemq.artemis.core.client.impl.ClientProducerImpl.doSend(ClientProducerImpl.java:263) > at > org.apache.activemq.artemis.core.client.impl.ClientProducerImpl.send(ClientProducerImpl.java:126) > at > org.apache.activemq.artemis.jms.client.ActiveMQMessageProducer.doSendx(ActiveMQMessageProducer.java:491) > at > org.apache.activemq.artemis.jms.client.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:189) > at javax.jms.QueueRequestor.request(QueueRequestor.java:54) > > Does anybody has any idea what can be wrong? I have attached my broker > config file. > > Note: > 1. My Artemis version is 1.5.3 > 2. There are no messages in the queue and also CPU load is around 30% > 3. I am using Embedded Artemis server using as Spring beans. > > > > -- > Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html >