[jira] Assigned: (AMQCPP-75) setCMSReplyTo with null destination segfaults when using Openwire wire format

["Timothy Bish (JIRA)" <ji...@apache.org>]

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

Timothy Bish reassigned AMQCPP-75:
----------------------------------

    Assignee: Timothy Bish  (was: Nathan Mittler)

> setCMSReplyTo with null destination segfaults when using Openwire wire format
> -----------------------------------------------------------------------------
>
>                 Key: AMQCPP-75
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-75
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Openwire
>    Affects Versions: 2.0
>            Reporter: Albert Strasheim
>         Assigned To: Timothy Bish
>             Fix For: 2.0
>
>
> In our code we call setCMSReplyTo with a null destination in a few places. This works fine with Stomp, which does a check for null destination argument, and if the argument is not null, deletes the existing destination and clones the argument.
> Openwire simply does this->setReplyTo(dynamic_cast<ActiveMQDestination*>(destination->clone())); which doesn't work if the argument is null.

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