activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Lugt (JIRA)" <j...@apache.org>
Subject [jira] Created: (AMQ-994) .Net client TcpTransport does not prevent concurrent access to BinaryWriter
Date Thu, 19 Oct 2006 11:51:17 GMT
.Net client TcpTransport does not prevent concurrent access to BinaryWriter
---------------------------------------------------------------------------

                 Key: AMQ-994
                 URL: https://issues.apache.org/activemq/browse/AMQ-994
             Project: ActiveMQ
          Issue Type: Bug
          Components: NMS (C# client)
    Affects Versions: 4.0.2
         Environment: Windows
            Reporter: Rob Lugt


A client application using multiple sessions may write multiple messages concurrently. The
underlying TcpTransport does not synchronize access to its BinaryWriter, resulting in possible
data message corruption or worse.

The TcpTransportFactory in the Java client uses a MutexTransport to protect the underlying
socket.  This technique would work equally well in the .Net client, but I propose simply locking
the writer as the TcpTransport should argueably protect itselft rather than relying on the
factory to provide protection.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message