activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQCPP-465) Periodic access violation originating from Openwire::unmarshal
Date Mon, 25 Feb 2013 23:44:12 GMT


Timothy Bish commented on AMQCPP-465:

Pushed new SNAPSHOT that includes the TcpSocket changes.  From my testing this seems to be
working fine.  Requires some hoop jumping to keep ServerSocket working as we get into some
tangles because of the APR memory pools and general limitations of APR but no issues in the
client code should link to that as the ServerSocket code doesn't come into play there.
> 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
>         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