activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQCPP-465) Periodic access violation originating from Openwire::unmarshal
Date Wed, 27 Feb 2013 15:53:12 GMT

    [ https://issues.apache.org/jira/browse/AMQCPP-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588456#comment-13588456
] 

Timothy Bish commented on AMQCPP-465:
-------------------------------------

SNAPSHOT was updated last night with some additional changes to get a better exception propagated
to the client when things like security exceptions are sent back from the broker.  You might
want to pull that down and sanity test.  I don't envision any further changes unless new critical
bugs get reported in the next few days.  I plan on rolling a release candidate next week time
permitting.  
                
> 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
>             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: http://www.atlassian.com/software/jira

Mime
View raw message