[
https://issues.apache.org/activemq/browse/AMQNET-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan moved AMQ-994 to AMQNET-15:
------------------------------------------
Fix Version/s: 1.0
Component/s: (was: NMS (C# client))
Affects Version/s: (was: 4.0.2)
Key: AMQNET-15 (was: AMQ-994)
Project: ActiveMQ .Net (was: ActiveMQ)
> .Net client TcpTransport does not prevent concurrent access to BinaryWriter
> ---------------------------------------------------------------------------
>
> Key: AMQNET-15
> URL: https://issues.apache.org/activemq/browse/AMQNET-15
> Project: ActiveMQ .Net
> Issue Type: Bug
> Environment: Windows
> Reporter: Rob Lugt
> Fix For: 1.0
>
> 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.
-
You can reply to this email to add a comment to the issue online.
