Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 85718 invoked from network); 3 Feb 2009 01:24:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Feb 2009 01:24:20 -0000 Received: (qmail 48473 invoked by uid 500); 3 Feb 2009 01:24:20 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 48449 invoked by uid 500); 3 Feb 2009 01:24:20 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 48437 invoked by uid 99); 3 Feb 2009 01:24:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2009 17:24:20 -0800 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of e.semog@gmail.com designates 74.125.44.156 as permitted sender) Received: from [74.125.44.156] (HELO yx-out-1718.google.com) (74.125.44.156) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Feb 2009 01:24:12 +0000 Received: by yx-out-1718.google.com with SMTP id 3so671567yxi.86 for ; Mon, 02 Feb 2009 17:23:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=QygwcAVYTu2+ZPEhVjFCscF0ZPTmbVmNYW11VLZpSL8=; b=a7NIFdb8Mks0BOqjyyVA9T75h4L3NhekbDfCHcYgebYpgMQkrE0sZbH6VkeyjRlUkl 78hxs3eVF2lZcyG5Vt5/Kp9ByJADf3CCXex8DuY0Ne5sjsgAzHsMdJQlQJIyQrQ1gOJw VmEBke1SYD9cjApcxrd/3UkqklhXam2qr4QOs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=k0gcjBt6aH7SeXN4Qsl1mQvrk7/FX5mJH3nOCuG9s+gzQbq3fy97+EbtCZtEWCsx+P xBo+R/JsSL14PZvTDFJoFsqSYH8aTHfSpkrqdhY4nJb6677IDXWsKOKGSWa5u41OrCPw x7x0yEHGY1g41+IcQZkLPJQ9ZO/eQ6T0Oy47E= MIME-Version: 1.0 Received: by 10.90.68.20 with SMTP id q20mr290480aga.11.1233624231810; Mon, 02 Feb 2009 17:23:51 -0800 (PST) In-Reply-To: <21588244.post@talk.nabble.com> References: <21588244.post@talk.nabble.com> Date: Mon, 2 Feb 2009 17:23:51 -0800 Message-ID: <5a56ce1b0902021723i59df686aw57e0bd07fdcae4d5@mail.gmail.com> Subject: Re: Is Apache.NMS.ISession thread safe? From: Jim Gomes To: dev@activemq.apache.org Content-Type: multipart/alternative; boundary=001636163f411f99150461f98650 X-Virus-Checked: Checked by ClamAV on apache.org --001636163f411f99150461f98650 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit There are currently a couple of JIRA issues related to threading issues. I have not verified these, nor have I run across them in my own usage patterns. However, they may be related to whatever issues you may be experiencing. Take at look at them and see if they might help you diagnose your issues: https://issues.apache.org/activemq/browse/AMQNET-136 https://issues.apache.org/activemq/browse/AMQNET-132 https://issues.apache.org/activemq/browse/AMQNET-113 Best, Jim On Wed, Jan 21, 2009 at 9:41 AM, sbs1982 wrote: > > If one thread in my app is trying to create a temporary topic and I already > have a few consumers(listening on other temp topics & processesing incoming > messages on their respective call back methods i.e listeners) open. Now > trying to call the close method of one of these consumers causes my app to > go into deadlock. > > > is there some know issue of close method of consumers locking? > > I looked at the code in the MessageConsumer..the first statement is > lock(this). > Some articles are out there saying that locking on this is unsafe? > > > > -- > View this message in context: > http://www.nabble.com/Is-Apache.NMS.ISession-thread-safe--tp21588244p21588244.html > Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. > > --001636163f411f99150461f98650--