Return-Path: 
 <dev-return-40381-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-dev-archive@www.apache.org
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6221C10900
	for <apmail-activemq-dev-archive@www.apache.org>;
 Thu, 12 Sep 2013 06:54:41 +0000 (UTC)
Received: (qmail 29397 invoked by uid 500); 12 Sep 2013 06:54:37 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 29354 invoked by uid 500); 12 Sep 2013 06:54:33 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 29169 invoked by uid 99); 12 Sep 2013 06:54:31 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Sep 2013 06:54:31 +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 (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.223.179 as permitted sender)
Received: from [209.85.223.179] (HELO mail-ie0-f179.google.com)
 (209.85.223.179)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Sep 2013 06:54:25 +0000
Received: by mail-ie0-f179.google.com with SMTP id e14so6690589iej.24
        for <dev@activemq.apache.org>; Wed, 11 Sep 2013 23:54:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=4AB4xECunIAj9nrnn/gPxQgYzQKVQYtIeq5lBMmym3s=;
        b=U5lCoVDKJLPteXe+9HdqRL+k9JX82vIfJy3/xeEV5J+zcqQ4tDQr/gE3Wnlxs1lgZN
         gl/KIqb3X9Tx45gIG7xfgCC2udmswx0K5dmllL/MRTNkou/liR/3KdQW8F2bC35GaVAd
         olZpAbo4bIiy8kbDxB56l0U5z3dgFJZqrHYLz85JOheKuWaR7yeDlTcF9w0DsNkYPZZj
         U0UXgpf64KB0y0mJoAyPq8cDwAqkXHvJUmur4QZxDFUY2IlvaxNujpwo20BsF66XgAmV
         ehSBmrZMxfi5xh2nb/qBSmiGWBCwp39lRTp2p1evRVjTV5Kaz9QwWnLW1d2G++0FWuRu
         py/g==
X-Received: by 10.50.73.74 with SMTP id j10mr12936953igv.50.1378968844979;
 Wed, 11 Sep 2013 23:54:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.20.196 with HTTP; Wed, 11 Sep 2013 23:53:43 -0700 (PDT)
In-Reply-To: <1378962709042-4671434.post@n4.nabble.com>
References: <1378962709042-4671434.post@n4.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Thu, 12 Sep 2013 08:53:43 +0200
Message-ID: 
 <CAGB5yNnA_XHeqRtZ7ZZT_UY7ap_9GggQoVWY=RSD-ps9aL3Z5Q@mail.gmail.com>
Subject: Re: Camel and Embedded AMQ. Problem consuming from a queue
To: dev@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

Hi

Can you tell us a bit more about real environment? eg what container
do you embed AMQ in?
And do you use AMQ 5.7.0 version?

And what about the code for handling the request/reply on the server
is this hand coded JMS code, or do you use Camel or some other
framework?

And what queue types do you use for the reply queue? Is it a temporary
queue or a named queue?
Also what about the clocks on the client and server, and they fairly
in sync? As you may hit a message expiry problem if the client and
broker clocks are not in sync.


On Thu, Sep 12, 2013 at 7:11 AM, Maximus_Developerius
<khudyakov.max@gmail.com> wrote:
>  Good day,
> I would realy appreciate your help, because I was unable to find the answer
> searching on the web.
> I'm facing the problem using an embedded AMQ Broker.
> The version of the broker is 5.7.0
> <dependency>
>     <groupId>org.apache.activemq</groupId>
>     <artifactId>activemq-core</artifactId>
>     <version>5.7.0</version>
> </dependency>
>
> I'm using the Request-Reply pattern, so at some point I expect the response
> during the specific timeout. And the communication may work few days, but
> sometimes the consumer, that expects the response can't consume the message
> from a response queue, however, the response message is sent. But can't be
> consumed by the consumer.
>
> When I use the standalone AMQ of the same version, then there is no such a
> problem.
> Here is the configuration of an embedded broker:  activemq.xml
> <http://activemq.2283324.n4.nabble.com/file/n4671434/activemq.xml>
>
> The only workaround, that I have right now to start it working is the remove
> of the kahadb folder, but is not a good solution for a production
> environment at all.
>
> What can be the reason of such a behaviour and what is a workaround?
> Maybe someone has already coped with the same problem or the similar one?
> Thanks in advance for your help.
>
> PS: I've tried to write a junit test and run it - can't reproduce. 1000000
> request-reply and no problem at all, but it happens, when that embedded
> broker is used on the real environments.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/Camel-and-Embedded-AMQ-Problem-consuming-from-a-queue-tp4671434.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen