[
https://issues.apache.org/jira/browse/AMQCPP-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506076#comment-13506076
]
Scott Weaver commented on AMQCPP-405:
-------------------------------------
I have not yet been able to recreate the access violation with the latest code.
However, I see an enormous amount of handled exceptions when running the code
without even disturbing the broker. Is this expected? I am roughly seeing the
following handled exceptions per thread:
1/thread First-chance exception at 0x7c812afb in MultiTest.exe: Microsoft C++
exception: decaf::lang::exceptions::RuntimeException at memory location
0x16cbf69c..
1/thread First-chance exception at 0x7c812afb in MultiTest.exe: Microsoft C++
exception: cms::CMSException at memory location 0x16cbf8d0..
1/thread First-chance exception at 0x7c812afb in MultiTest.exe: Microsoft C++
exception: decaf::io::EOFException at memory location 0x16fbfc70..
3/thread First-chance exception at 0x7c812afb in MultiTest.exe: Microsoft C++
exception: [rethrow] at memory location 0x00000000..
This may not be anything new but is surely a performance drag. We will continue
to test this latest version and keep you updated. Thanks for your assistance!
> 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: cmstest.7z, CMS_Test_Tool.7z, cmstest-vs2008.7z,
> CrashHang_Report__CMSMessageHandlerCOM-TestMultipleSendersReceivers.exe__11072012173926312.mht,
>
> CrashHang_Report__CMSMessageHandlerCOM-TestReceiver.exe__10242012114621213.mht,
> 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,
> CrashHang_Report__SCOTApp.exe__10272012120620437.mht,
> CrashHang_Report__SCOTApp_exe__11012012195321234.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