[jira] Updated: (AMQCPP-109) Exception when acknowledging null messages, originating from the receipt of an ObjectMessage

["Nathan Mittler (JIRA)" <ji...@apache.org>]

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

Nathan Mittler updated AMQCPP-109:
----------------------------------

    Fix Version/s:     (was: 2.0)
                   2.0.1

> Exception when acknowledging null messages, originating from the receipt of an ObjectMessage 
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-109
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-109
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Openwire
>    Affects Versions: 2.0
>         Environment: Machine: Windows XP
> Broker: ActiveMQ 4.1.1
> Various client javaapplications producing ByteMessages, TextMessages and ObjectMessages.
> A single C++ application built with Visual C++ 2005.
>            Reporter: Brendan Cashman
>         Assigned To: Nathan Mittler
>             Fix For: 2.0.1
>
>
> The single C++ client that wants to consume TextMessages and simply ignore the ObjectMessages.  In the current configuration the C++ app receives null messages for each ObjectMessage.  When using Openwire, the connector tries to
> acknowledge the null message and throws an OpenwireConnectionException (see line 973 of OpenWireConnector::acknowledge from release 2.0).
> The acknowledge mode in the Session is set to DUPS_OK_ACKNOWLEDGE, but it appears (from looking at the source) that this issue will occur in other modes.
> It looks like this problem won't occur using Stomp unless the acknowledge mode is set to CLIENT_ACKNOWLEDGE. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.