activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Helen Huang (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQCPP-454) Found pure function call error in CMS
Date Wed, 06 Feb 2013 21:03:14 GMT

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

Helen Huang edited comment on AMQCPP-454 at 2/6/13 9:01 PM:
------------------------------------------------------------

I am wondering if there is any way to prevent the usage of an InactivityMonitor that is still
under construction... It might be better than checking if memebers is NULL in the stopMonitorThreads
function. Because even if memebers is not NULL, it's  properties can be still under construction.
                
      was (Author: hhuang):
    I am wondering if there is any way to prevent the usage of an InactivityMonitor that is
still under construction... It might be better than checking if this->memebers is NULL
in the stopMonitorThreads function.
                  
> Found pure function call error in CMS
> -------------------------------------
>
>                 Key: AMQCPP-454
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-454
>             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.5.0
>
>         Attachments: cmstemplate-stress.zip, CrashHang_Report__CMSMessageHandler-MultiTest_exe__02052013182239896.mht
>
>
> WeEncountered a pure function call error in CMS during our test. The following is the
call stack:
> 	msvcr80d.dll!_NMSG_WRITE(int rterrnum=0x00000019)  Line 198	C
>  	msvcr80d.dll!_purecall()  Line 54 + 0x7 bytes	C
>  	activemq-cppud.dll!decaf::util::concurrent::Lock::lock()  Line 55	C++
>  	activemq-cppud.dll!decaf::util::concurrent::Lock::Lock(decaf::util::concurrent::Synchronizable
* object=0x0cb6de90, const bool intiallyLocked=true)  Line 34	C++
>  	activemq-cppud.dll!activemq::transport::inactivity::InactivityMonitor::stopMonitorThreads()
 Line 469 + 0x20 bytes	C++
>  	activemq-cppud.dll!activemq::transport::inactivity::InactivityMonitor::onException(const
decaf::lang::Exception & ex={...})  Line 310	C++
>  	activemq-cppud.dll!activemq::transport::TransportFilter::fire(const decaf::lang::Exception
& ex={...})  Line 53 + 0x17 bytes	C++
>  	activemq-cppud.dll!activemq::transport::TransportFilter::onException(const decaf::lang::Exception
& ex={...})  Line 46	C++
>  	activemq-cppud.dll!activemq::transport::IOTransport::fire(decaf::lang::Exception &
ex={...})  Line 64 + 0x17 bytes	C++
>  	activemq-cppud.dll!activemq::transport::IOTransport::run()  Line 259	C++
>  	activemq-cppud.dll!decaf::lang::Thread::run()  Line 143	C++
>  	activemq-cppud.dll!`anonymous namespace'::runCallback(void * arg=0x0c85e460)  Line
262 + 0x11 bytes	C++
>  	activemq-cppud.dll!`anonymous namespace'::threadEntryMethod(void * arg=0x0c85e460)
 Line 250 + 0x15 bytes	C++
>  	msvcr80d.dll!_callthreadstartex()  Line 348 + 0xf bytes	C
>  	msvcr80d.dll!_threadstartex(void * ptd=0x1898e470)  Line 331	C
>  	kernel32.dll!7c80b729() 	
>  	[Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]

> We have 25 senders and receivers in our test, and we restart the broker every 10 seconds.

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

Mime
View raw message