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 554DF10AF3 for ; Mon, 7 Oct 2013 10:37:44 +0000 (UTC) Received: (qmail 17254 invoked by uid 500); 7 Oct 2013 10:37:43 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 17023 invoked by uid 500); 7 Oct 2013 10:37:42 -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 17015 invoked by uid 99); 7 Oct 2013 10:37:41 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Oct 2013 10:37:41 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com designates 209.85.223.180 as permitted sender) Received: from [209.85.223.180] (HELO mail-ie0-f180.google.com) (209.85.223.180) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Oct 2013 10:37:37 +0000 Received: by mail-ie0-f180.google.com with SMTP id u16so15014528iet.39 for ; Mon, 07 Oct 2013 03:37:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=km1hBfYeKYb/7MktXDm7JRHZi8zxScjysneQIb/qH8k=; b=qi4AI+iRIylhAPaHC1Mg/nn9sZXlssy0uG82Kcl6t5tsfG7w1Agrqfkrb/yVVEXL+e Yyk7gXwrtbdCibyKGYOvjRKRd5eRd1PPN2pfN1vdnPIxVAO0YaUHhOknv+AloZ5QvVN3 CfC7erI/fjmnTQHk4wwzy2AvgahUc9/qanETFfB8pOauGvbFkyW1DCJ7vLEJVBiR7xnK 69zYJ0Xo33MQssZ9WI6pIf77puBFnTtyRefj7Dvat/+jPSnEYzzSp4iT7qjyfG4lbUqu V0s2+HmzYDkq8tYy285whGCb0ntbsKLqYas5uXxOQgPAlAgnk8qdynjCCz4uICVMWLeo bCDw== MIME-Version: 1.0 X-Received: by 10.50.9.72 with SMTP id x8mr16646490iga.19.1381142236724; Mon, 07 Oct 2013 03:37:16 -0700 (PDT) Received: by 10.64.28.161 with HTTP; Mon, 7 Oct 2013 03:37:16 -0700 (PDT) In-Reply-To: <1380898722486-4672276.post@n4.nabble.com> References: <1380898722486-4672276.post@n4.nabble.com> Date: Mon, 7 Oct 2013 11:37:16 +0100 Message-ID: Subject: Re: Deadlock when using XA and PFC From: Gary Tully To: "users@activemq.apache.org" Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org a thread dump of the broker will show you exactly where a thread is blocked. But if pfc is the limit, there will be an indication in the log - slf4j On 4 October 2013 15:58, dumlebert wrote: > Hi, > I have an issue that I've battled with for some time now and I'm running out > of ideas. We're using ActiveMQ from MuleESB. The flow in this case reads a > message from one queue, splits it into several messages and puts them on > another queue. All this is done within an XA transaction. The messages are > up to a few MB each. > > When the producer (our flow) has put say 3/5 messages on the queue, it hangs > when trying to publish the 4th message. This gets into a deadlock, as the > consumer can't consume the messages until the producer commits, and the > producer is not allowed to publish the messages it needs to commit the XA > transaction. > > It's logical to think that PFC together with XA could create this kind of > situation, but I'm unable to verify that it actually is PFC that is stopping > the producer from publishing all messages. I've tried to: > - disable PFC (verified by viewing the attributes through jmx) > - set the sendFailIfNoSpace = "true" > - increase the memoryUsage, storeUsage and tempUsage to high values > > Nothing changes the behaviour. > > If I cut the size of the messages to be produced by limiting the amount of > data they include, all messages a published and the XA commits just fine. So > the hangup does seem to be related to size. > > But then, why is the problem the same when disabling PFC. I must be missing > something here... > > I want to be dead certain on exactly what is the problem that cause the send > to queue to hang. I'm really thankful for any ideas on how I can figure out > what is going on. > > > > -- > View this message in context: http://activemq.2283324.n4.nabble.com/Deadlock-when-using-XA-and-PFC-tp4672276.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- http://redhat.com http://blog.garytully.com