[
https://issues.apache.org/jira/browse/AMQCPP-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13586473#comment-13586473
]
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.
http://people.apache.org/~tabish/cms-3.6.x/
> 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, 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: http://www.atlassian.com/software/jira
