Return-Path: X-Original-To: apmail-qpid-users-archive@www.apache.org Delivered-To: apmail-qpid-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 CEB011797E for ; Wed, 28 Jan 2015 09:00:33 +0000 (UTC) Received: (qmail 54885 invoked by uid 500); 28 Jan 2015 09:00:34 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 54845 invoked by uid 500); 28 Jan 2015 09:00:34 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 54812 invoked by uid 99); 28 Jan 2015 09:00:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jan 2015 09:00:30 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of keith.wall@gmail.com designates 209.85.220.181 as permitted sender) Received: from [209.85.220.181] (HELO mail-vc0-f181.google.com) (209.85.220.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Jan 2015 09:00:26 +0000 Received: by mail-vc0-f181.google.com with SMTP id id10so6359579vcb.12 for ; Wed, 28 Jan 2015 01:00:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=hHQFAUS/DJru7KE31RBXkwHMS1mRa6RmIDVtlMeT9zs=; b=hw6zTymInD4Y+uPMBz7iqfccn5cIzVJWXvlDoRliJt+Ol2ZW4TsMbYLODGKLDdKd8X 8jCh6bupHuOcRQG+9PWPPrztt99u1AuW7t0y2ja95i/BuAM6OeKIh3Y9H3xXZWl54wZp yw3pWtc7vbGrqQ4Ea9Mwzzi/Up2Q/K265ZMNTQMNeHPUhd6WRchv/gchbo6jE5XYJB1U 0pzUXJwBHPXEFsYuhSwzeBlgHjSTqP87rdxxB8ub2QTB8v8y7bTHD3gWh3rEs7y3ZGXC X8kvSwuCTou8eojgz5V6xizToV2ErlyLqS8J06XRizkqn+MUJsnIlehxUcWBxyhNuCd/ UXJg== MIME-Version: 1.0 X-Received: by 10.52.75.202 with SMTP id e10mr985540vdw.73.1422435606113; Wed, 28 Jan 2015 01:00:06 -0800 (PST) Received: by 10.52.141.38 with HTTP; Wed, 28 Jan 2015 01:00:05 -0800 (PST) Reply-To: keith.wall@gmail.com In-Reply-To: <1421916534888-7618696.post@n2.nabble.com> References: <1421916534888-7618696.post@n2.nabble.com> Date: Wed, 28 Jan 2015 09:00:05 +0000 Message-ID: Subject: Re: Qpid JMS: Message listener blocks other message listener on different session From: Keith W To: "users@qpid.apache.org" Content-Type: multipart/alternative; boundary=20cf3071ca4404b3b3050db299ed X-Virus-Checked: Checked by ClamAV on apache.org --20cf3071ca4404b3b3050db299ed Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Erik Can you tell us a little more about your software stack? Which Broker/version are you using (Qpid Cpp, Qpid Java, something else non-Qpid)? There are two distinct Qpid JMS clients at the moment, the 0-8..0-10 client (i.e. qpid-client-x.xx-bin.tar.gz) and the AMQP 1.0 client (i.e. qpid-amqp-1-0-client-jms-x.xx-bin.tar.gz)? I guess from your previous list interactions that it is the latter. Can you confirm? Do you have a thread dump (jstack -l) when the problem occurs? Kind regards, Keith On 22 January 2015 at 08:48, Erik Aschenbrenner wrote: > > Dear Qpid Users, > > I have an application where I'm using different message listeners to process > data from different topics. > > For example I have a message listener which processes reference data > received via a broadcast topic and another message listener which processes > market data like trades and orders received on another broadcast topic. > > Both message listeners are created by a dedicated JMS session (one sessio= n > for each message listener). > > Because the market data can only be processed if all the reference data was > processed initially, the message listener for the market data should wait > and block if the reference data was not received completely. > > So here the problem: if the thread of the message listener for market dat= a > is blocked, the receiving of the reference data is also blocked an no other > data is received on the reference data listener. > > Why are there dependencies between message listeners on different session= ? > As far as I understand each session should have it=C2=B4s on thread? > > Regards, > Erik > > > > > -- > View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-JMS-Message-listener-blocks-other-me= ssage-listener-on-different-session-tp7618696.html > Sent from the Apache Qpid users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org > For additional commands, e-mail: users-help@qpid.apache.org > --20cf3071ca4404b3b3050db299ed--