[
https://issues.apache.org/jira/browse/AMQCPP-451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571817#comment-13571817
]
Helen Huang commented on AMQCPP-451:
------------------------------------
Could you please let us know how you did the test? Maybe there are some
differences between the way we did the test. Are you running on Lunix or
Windows? We found the leak on windows. Also, if you increase the frequence that
you restart the broker you might be able to find the leak more often. We use a
batch file to restart the broker. My batch lookes like the following.
:TOP
net start activemq
ping 127.0.0.1 -n 31 > nul
net stop activemq
ping 127.0.0.1 -n 31 > nul
GOTO TOP
I think scott restart the broker more often than me.
> The number of CMS threads increases when we restart the message broker
> repeatedly
> ----------------------------------------------------------------------------------
>
> Key: AMQCPP-451
> URL: https://issues.apache.org/jira/browse/AMQCPP-451
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Affects Versions: 3.5.0
> 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: cmstemplate-stress.zip,
> CrashHang_Report__CMHMultiTestWithCom.exe__02012013222736766.mht
>
>
> The number of CMS threads increases when we restart the message broker
> repeatedly. We have ten senders and ten receivers in out test. Every sender
> sends out 10-20 messages every second. We restart the broker every 1 minute.
> The number of threads in CMS grew from about 50 to 600 after about 15 hours
> of testing. The attached dump was created after we ran two hours of test.
> From the dump we find a large number of threads are stuck at the following
> place:
> Function Source
> ntdll!KiFastSystemCallRet
> ntdll!ZwWaitForSingleObject+c
> kernel32!WaitForSingleObjectEx+a8
> kernel32!WaitForSingleObject+12
> activemq_cppud!decaf::internal::util::concurrent::PlatformThread::interruptibleWaitOnCondition+25
>
> activemq_cppud!`anonymous namespace'::threadEntryMethod+9b
> msvcr80d!_callthreadstartex+51
> msvcr80d!_threadstartex+87
> kernel32!BaseThreadStart+37
--
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