[ https://issues.apache.org/activemq/browse/AMQ-994?page=all ]
Rob Lugt closed AMQ-994.
------------------------
Resolution: Won't Fix
The writer is already protected by a MutexTransport in .Net just as it is in
Java. How did I miss this??
> .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
> Attachments: patch-amq994.txt
>
>
> 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
