[
https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13479260#comment-13479260
]
Helen Huang commented on AMQCPP-405:
------------------------------------
Hi Timothy,
I got two errors when I was trying to compile the latest code. Could you please
take a look?
Thanks!
HashMap.cpp
c:\FL42BLDTREE\build\Third Party
Software\ActiveMQCPP\activemq-cpp\src\main\decaf/util/HashCode.h(92) : error
C2766: explicit specialization; 'decaf::util::HashCode<wchar_t>' has already
been defined
c:\FL42BLDTREE\build\Third Party
Software\ActiveMQCPP\activemq-cpp\src\main\decaf/util/HashCode.h(81) : see
previous definition of 'HashCode<unsigned short>'
HashCode.cpp
c:\fl42bldtree\build\third party
software\activemqcpp\activemq-cpp\src\main\decaf\util\HashCode.h(92) : error
C2766: explicit specialization; 'decaf::util::HashCode<wchar_t>' has already
been defined
c:\fl42bldtree\build\third party
software\activemqcpp\activemq-cpp\src\main\decaf\util\HashCode.h(81) : see
previous definition of 'HashCode<unsigned short>'
> 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__CMSMessageHandlerCOM-TestSender_exe__1001201211243973.mht,
> CrashHang_Report__CMSMessageHandlerCOM-TestSender_exe__1001201220471946.mht,
> CrashHang_Report__CMSMessageHandlerCOM-TestSender_exe__10022012152424484.mht,
> CrashHang_Report__CMSMessageHandlerCOM-TestSender_exe__10032012172730765.mht,
> 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
