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 Thu, 21 Feb 2013 21:18:12 GMT


Timothy Bish commented on AMQCPP-465:

My guess is that the issue is in TcpSocket.  I'm thinking that the socket is closed right
before an attempt by IOTransport to enter another blocking read and since the code closes
the socketHandle in an attempt unblock the readers that the recv call ends up using a bad
value in apr_socket_recv.  
> 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__PID_10568__02212013121958303.mht, CrashHang_Report__PID_12904__02212013122442266.mht,
CrashHang_Report__PID_13840__02212013122742886.mht, CrashHang_Report__PID_3816__02212013122319960.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:

View raw message