activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <j...@apache.org>
Subject [jira] Closed: (AMQNET-49) Deadlock and race condition in TcpTransport
Date Wed, 13 Feb 2008 00:32:36 GMT

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

Jim Gomes closed AMQNET-49.
---------------------------

    Resolution: Fixed

> Deadlock and race condition in TcpTransport
> -------------------------------------------
>
>                 Key: AMQNET-49
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-49
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client
>         Environment: Windows XP SP2, .NET 2.0
>            Reporter: Jim Gomes
>            Assignee: James Strachan
>         Attachments: amqnet-49.patch.txt
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message