[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Commented] (AMQCPP-405) CMS sender thread hangs after restarting broker
From:       "Timothy Bish (JIRA)" <jira () apache ! org>
Date:       2012-09-29 18:04:07
Message-ID: 14659726.143424.1348941847597.JavaMail.jiratomcat () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin. \
system.issuetabpanels:comment-tabpanel&focusedCommentId=13466275#comment-13466275 ] 

Timothy Bish commented on AMQCPP-405:
-------------------------------------

The code actually returns a reference to a Collection<E> type so you can either \
create a reference or assign the return value to a concrete type link LinkedList<E> \
or ArrayList<E> depending on what you plan to do with the result.  You can take a \
look at the unit tests for the StlMap and HashMap classes.  This change allow the \
returned value to simply be a reference to some internal proxy object that doesn't \
require copying everything in the Map's values or keys so its much more efficient.  \
You code code look as follows:

{code}

Collection<std::string>& values = someMap.values();

{code}


                
> CMS sender thread hangs after restarting broker
> -----------------------------------------------
> 
> Key: AMQCPP-405
> URL: https://issues.apache.org/jira/browse/AMQCPP-405
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: CMS Impl
> Affects Versions: 3.4.1
> Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util \
>                 1.3.9, apr iconv 1.2.1
> Reporter: Helen Huang
> Assignee: Timothy Bish
> Priority: Critical
> Fix For: 3.5.0
> 
> Attachments: CrashHang_Report__PID_2832__05232012143544484.mht
> 
> 
> The sender thread in CMS hangs after we retarted the message broker.
> The thread is 548 in the attached dump file. 
> This is a critical issue that blocks the release of our product that is scheduled \
> in a few days. We hope you can resolve it soon. Really appreciate your help!

--
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


[prev in list] [next in list] [prev in thread] [next in thread]