Return-Path: 
 <dev-return-36634-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 1AFEAE379
	for <apmail-activemq-dev-archive@www.apache.org>;
 Thu, 14 Feb 2013 18:37:13 +0000 (UTC)
Received: (qmail 3040 invoked by uid 500); 14 Feb 2013 18:37:12 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 3011 invoked by uid 500); 14 Feb 2013 18:37:12 -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 3002 invoked by uid 99); 14 Feb 2013 18:37:12 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2013 18:37:12 +0000
Date: Thu, 14 Feb 2013 18:37:12 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12630844.1360058163109.289743.1360867032783@arcas>
In-Reply-To: <JIRA.12630844.1360058163109@arcas>
References: <JIRA.12630844.1360058163109@arcas>
Subject: [jira] [Closed] (AMQCPP-453) Persistence Flag ActiveMQ C++ - WRONG
 FLAG CONSTANTS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/AMQCPP-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQCPP-453.
-------------------------------

    Resolution: Not A Problem

I can't find any issues here.  Closing, if you can produce a test case against the current release please comment here and I will reopen.  
                
> Persistence Flag ActiveMQ C++ - WRONG FLAG CONSTANTS
> ----------------------------------------------------
>
>                 Key: AMQCPP-453
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-453
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 2.1.1, 3.5.0
>         Environment: SuSe Linux
>            Reporter: Nikolaus Klimek
>            Assignee: Timothy Bish
>            Priority: Minor
>              Labels: bug
>
> We are using the ActiveMQ Broker 5.6.0 and the ActiveMQ C++ Client 2.1.1,
> both running on SuSe Linux. We have the problem, that setting persistence in the C++-client doenst effect at the broker. The Messages in the broker are non-persistent, although we have set persistence in the activemq.xml, too.
> [...]
>  <broker xmlns="http://activemq.apache.org/schema/core" brokerName="localhost" dataDirectory="${activemq.data}" persistent="true">
>         <!--
>             For better performances use VM cursor and small memory limit.
>             For more information, see:
>             http://activemq.apache.org/message-cursors.html
>             Also, if your producer is "hanging", it's probably due to producer flow control.
>             For more information, see:
>             http://activemq.apache.org/producer-flow-control.html
>         -->
> [...]
> For my unterstanding, the Broker uses javax.jms.DeliveryMode for checking, if the Message is PERSISTENT or NON_PERSISTENT. Looking into the constant-spec. for java.jmx.DeliveryMode shows: 
> javax.jms.DeliveryMode
> public static final int 	NON_PERSISTENT 	1
> public static final int 	PERSISTENT 	2
> In the C++-Client-Application, we set 
> producer->setDeliveryMode(DeliveryMode::PERSISTENT);
> Looking into activemq-cpp/src/main/cms/DeliveryMode.h shows:
> [...]
> enum DELIVERY_MODE {
>             PERSISTENT = 0,
>             NON_PERSISTENT = 1
>         };
> [...]
> Setting producer->setDeliveryMode(2) works for us. So my question is:
> Is this a Bug or are there other possibilities to configure it right?
> Looking into activemq-cpp/src/main/cms/DeliveryMode.h of the C++-Clients version 3.5 shows still 0 and 1 for PERSISNT and NON_PERSISTENT. Should this be changed to 1 and 2?
>   
> Thank you and best regards
> Klimek

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira