activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <jira+amq...@apache.org>
Subject [jira] Updated: (AMQNET-49) Deadlock and race condition in TcpTransport
Date Wed, 02 Feb 2011 17:03:35 GMT

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

Jim Gomes updated AMQNET-49:
----------------------------

    Parent:     (was: AMQNET-68)

> Deadlock and race condition in TcpTransport
> -------------------------------------------
>
>                 Key: AMQNET-49
>                 URL: https://issues.apache.org/jira/browse/AMQNET-49
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ
>         Environment: Windows XP SP2, .NET 2.0
>            Reporter: Jim Gomes
>            Assignee: james strachan
>         Attachments: amqnet-49.patch.txt
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> If a read error occurs on the TCP socket reader, a deadlock can occur while attempting
to clean up the connection objects.  An upper level object may have issued a Synchronous request
that requires a response and will block forever waiting for a response from the broken connection.
 The transport needs to return an error response to the command handler to allow it to unblock
and avoid the deadlock condition.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message