activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Strasheim (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQCPP-75) setCMSReplyTo with null destination segfaults when using Openwire wire format
Date Sun, 11 Mar 2007 22:36:34 GMT

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

Albert Strasheim commented on AMQCPP-75:
----------------------------------------

Tested with AMQCPP 2.0 snapshot revision 517012.

> 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: Nathan Mittler
>
> 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.


Mime
View raw message