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

Helen Huang edited comment on AMQCPP-459 at 2/15/13 4:19 PM:
-------------------------------------------------------------

I looked at the call stack at the crash, and found the ThreadPoolExecutor was 
still in the awaitTermination routine. So it is not what you have guessed that 
the ThreadPoolExecutor had given up ... It could be something else.

        msvcr80d.dll!_heap_alloc_dbg(unsigned int nSize=0x01085290, int 
nBlockUse=0x00002710, const char * szFileName=0x00000000, int nLine=0x00000000) 
 Line 477 + 0x7 bytes   C++
        
activemq-cppud.dll!decaf::internal::util::concurrent::Threading::park(decaf::lang::Thread
 * thread=0x01085378, __int64 mills=0x0000000000002710, int nanos=0x00000000)  
Line 1399 + 0x23 bytes  C++
        
activemq-cppud.dll!decaf::util::concurrent::locks::LockSupport::parkNanos(__int64
 nanos=0x0000000000000000)  Line 70 + 0x1d bytes       C++
        
activemq-cppud.dll!decaf::util::concurrent::locks::DefaultConditionObject::awaitNanos(__int64
 nanosTimeout=0x00000002540be400)  Line 1183 + 0xd bytes   C++
        
activemq-cppud.dll!decaf::util::concurrent::ExecutorKernel::awaitTermination(__int64
 timeout=0x0000000000002710, const decaf::util::concurrent::TimeUnit & 
unit={...})  Line 903 + 0x2c bytes   C++
        
activemq-cppud.dll!decaf::util::concurrent::ThreadPoolExecutor::awaitTermination(__int64
 timeout=0x0000000000002710, const decaf::util::concurrent::TimeUnit & 
unit={...})  Line 1543 + 0x17 bytes      C++
        CMStressUD.exe!CmsAdapter::MessagingTask::TerminateThreads()  Line 70 + 
0x22 bytes      C++
>       CMStressUD.exe!wmain(int argc=0x0000000c, wchar_t * * argv=0x00bca220)  
> Line 342        C++
        CMStressUD.exe!__tmainCRTStartup()  Line 594 + 0x19 bytes       C
        CMStressUD.exe!wmainCRTStartup()  Line 414      C
        kernel32.dll!7c817077()         

                
      was (Author: hhuang):
    I looked at the call stack at the crash, and found the ThreadPoolExecutor 
was still in the awaitTermination routine. So it is not what you have guessed 
that the ThreadPoolExecutor had given up...

        msvcr80d.dll!_heap_alloc_dbg(unsigned int nSize=0x01085290, int 
nBlockUse=0x00002710, const char * szFileName=0x00000000, int nLine=0x00000000) 
 Line 477 + 0x7 bytes   C++
        
activemq-cppud.dll!decaf::internal::util::concurrent::Threading::park(decaf::lang::Thread
 * thread=0x01085378, __int64 mills=0x0000000000002710, int nanos=0x00000000)  
Line 1399 + 0x23 bytes  C++
        
activemq-cppud.dll!decaf::util::concurrent::locks::LockSupport::parkNanos(__int64
 nanos=0x0000000000000000)  Line 70 + 0x1d bytes       C++
        
activemq-cppud.dll!decaf::util::concurrent::locks::DefaultConditionObject::awaitNanos(__int64
 nanosTimeout=0x00000002540be400)  Line 1183 + 0xd bytes   C++
        
activemq-cppud.dll!decaf::util::concurrent::ExecutorKernel::awaitTermination(__int64
 timeout=0x0000000000002710, const decaf::util::concurrent::TimeUnit & 
unit={...})  Line 903 + 0x2c bytes   C++
        
activemq-cppud.dll!decaf::util::concurrent::ThreadPoolExecutor::awaitTermination(__int64
 timeout=0x0000000000002710, const decaf::util::concurrent::TimeUnit & 
unit={...})  Line 1543 + 0x17 bytes      C++
        CMStressUD.exe!CmsAdapter::MessagingTask::TerminateThreads()  Line 70 + 
0x22 bytes      C++
>       CMStressUD.exe!wmain(int argc=0x0000000c, wchar_t * * argv=0x00bca220)  
> Line 342        C++
        CMStressUD.exe!__tmainCRTStartup()  Line 594 + 0x19 bytes       C
        CMStressUD.exe!wmainCRTStartup()  Line 414      C
        kernel32.dll!7c817077()         

                  
> Found an access violation in NodePool::ReturNode(Node* node)
> ------------------------------------------------------------
>
>                 Key: AMQCPP-459
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-459
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    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.6.0
>
>         Attachments: CMStress.zip, 
> CrashHang_Report__CMStressUD.exe__02142013143459322.mht
>
>
> Caught an access violation in NodePool::ReturNode(Node* node)
> The following is the call stack:
> activemq-cppud.dll!`anonymous 
> namespace'::NodePool::returnNode(`anonymous-namespace'::Node * 
> node=0x05237488)  Line 311 + 0x6 bytes
> activemq-cppud.dll!decaf::util::concurrent::locks::DefaultConditionObject::unlinkCancelledWaiters()
>   Line 1450
> activemq-cppud.dll!decaf::util::concurrent::locks::DefaultConditionObject::await()
>   Line 1145
> CmsMessageHandlerCOMUD.dll!decaf::util::concurrent::LinkedBlockingQueue<decaf::lang::Runnable
>  *>::take()  Line 435 + 0x32 bytes
> activemq-cppud.dll!decaf::util::concurrent::ExecutorKernel::getTask()  Line 
> 1288 + 0x24 bytes
> activemq-cppud.dll!decaf::util::concurrent::ExecutorKernel::runWorker(decaf::util::concurrent::ExecutorKernel::Worker
>  * w=0x052359b8)  Line 720 + 0xe bytes
> activemq-cppud.dll!decaf::util::concurrent::ExecutorKernel::Worker::run()  
> Line 184
> activemq-cppud.dll!decaf::lang::Thread::run()  Line 143
> activemq-cppud.dll!`anonymous namespace'::runCallback(void * arg=0x0523a690)  
> Line 262 + 0x11 bytes
> activemq-cppud.dll!`anonymous namespace'::threadEntryMethod(void * 
> arg=0x0523a690)  Line 250 + 0x15 bytes
> msvcr80d.dll!_callthreadstartex()  Line 348 + 0xf bytes
> msvcr80d.dll!_threadstartex(void * ptd=0x0523ab30)  Line 331
> kernel32.dll!7c80b729() 
>  

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

Reply via email to