activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Weaver (JIRA)" <>
Subject [jira] [Resolved] (AMQCPP-465) Periodic access violation originating from Openwire::unmarshal
Date Tue, 26 Feb 2013 17:02:13 GMT


Scott Weaver resolved AMQCPP-465.

       Resolution: Fixed
    Fix Version/s: 3.6.0

Ran over the weekend for 39 hours straight until a hang was encountered. More than just the
test was hung so cannot attribuite it to this code. Restarted the test yesterday without an
attached debugger and have been running for over 26 hours straight with no issues. We are
confident this access violation has been fixed. I will mark this JIRA resolved and let you
close it once you have a release containing the fixes. Thanks again for hardening this component.
We have gone from not being able to run extreme tests for more than ten minutes to at least
39 hours now.
> Periodic access violation originating from Openwire::unmarshal
> --------------------------------------------------------------
>                 Key: AMQCPP-465
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Openwire
>    Affects Versions: 3.6.0
>         Environment: Windows XPSP3 VS2005
>            Reporter: Scott Weaver
>            Assignee: Timothy Bish
>             Fix For: 3.6.0
>         Attachments: CrashHang_Report__CMStressD.exe__02222013114744533.mht, CrashHang_Report__PID_10568__02212013121958303.mht,
CrashHang_Report__PID_12904__02212013122442266.mht, CrashHang_Report__PID_13840__02212013122742886.mht,
CrashHang_Report__PID_3816__02212013122319960.mht, CrashHang_Report__PID_8784__02212013122829943.mht,
TcpSocket.cpp, TcpSocket.h
> Running a sustained test produced 5 separate access violations all within the Openwire::unmarshal.
It appears only one occurred during termination. Attaching all 5 dumps.

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:

View raw message