activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Weaver (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQCPP-465) Periodic access violation originating from Openwire::unmarshal
Date Fri, 22 Feb 2013 17:58:12 GMT

     [ https://issues.apache.org/jira/browse/AMQCPP-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Scott Weaver updated AMQCPP-465:
--------------------------------

    Attachment: CrashHang_Report__CMStressD.exe__02222013114744533.mht

Your assumption appears to be absolutely correct. Adding another dump with thread 2 closing
the IOTransport and then joining thread 7 which is in TcpSocket::read. Line 611 checked the
socket and it was not closed there but it was closed by the time the thread reached line 649
where socketHandle was NULL. Note that it took 10.5 hours to recreate. Looks like about a
small 9 LOC window. The write probably suffers from the same issue but probably not as frequent.

                
> Periodic access violation originating from Openwire::unmarshal
> --------------------------------------------------------------
>
>                 Key: AMQCPP-465
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-465
>             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
>
>
> 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: http://www.atlassian.com/software/jira

Mime
View raw message