Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 76306 invoked from network); 27 May 2009 12:56:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 May 2009 12:56:42 -0000 Received: (qmail 89561 invoked by uid 500); 27 May 2009 12:56:55 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 89536 invoked by uid 500); 27 May 2009 12:56:55 -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 89519 invoked by uid 99); 27 May 2009 12:56:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 May 2009 12:56:54 +0000 X-ASF-Spam-Status: No, hits=1.1 required=10.0 tests=FORGED_HOTMAIL_RCVD2,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 May 2009 12:56:44 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1M9IgB-0000zh-FK for users@activemq.apache.org; Wed, 27 May 2009 05:56:23 -0700 Message-ID: <23741962.post@talk.nabble.com> Date: Wed, 27 May 2009 05:56:23 -0700 (PDT) From: Websphere and ActiveMQ To: users@activemq.apache.org Subject: Re: Now another problem appears In-Reply-To: <3a73c17c0905270346n6bbb8387h54d47498d676bce4@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: derrickcui@hotmail.com References: <23731817.post@talk.nabble.com> <3a73c17c0905270346n6bbb8387h54d47498d676bce4@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Thanks, Well, I used queueReceiver.receiveNoWait() method to receive message, but this method had not this issue when I used IBM MQ as MQM. I cannot use message listener here because it's client trigger the receiving message behaviour. Gary Tully wrote: > > If you are using consumer.receive(), add a small timeout to give the > broker > a chance to see your subscription, like receive(500). The MDB probably > uses > a message listener, you could use that approach in your java client also. > > > 2009/5/26 Websphere and ActiveMQ > >> >> Right now I can receive message from ActiveMQ on linux by Java Client, >> but >> I >> have to run java client many many times, then I can receive the message. >> However, J2EE MDB hasn't this problem, every times I use Java client to >> send >> message, it can receive message on time. >> >> I use default setting for ActiveMQ. >> -- >> View this message in context: >> http://www.nabble.com/Now-another-problem-appears-tp23731817p23731817.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >> >> > > > -- > http://blog.garytully.com > > Open Source SOA > http://FUSESource.com > > -- View this message in context: http://www.nabble.com/Now-another-problem-appears-tp23731817p23741962.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.