summaryrefslogtreecommitdiff
path: root/dotnet/Qpid.Client/Client/AMQConnection.cs
diff options
context:
space:
mode:
authorSteven Shaw <steshaw@apache.org>2006-11-28 20:29:56 +0000
committerSteven Shaw <steshaw@apache.org>2006-11-28 20:29:56 +0000
commitc4fac88720bbfbaacbd821596d46e8715a161639 (patch)
treede07d81c5be72af718b637bd8095f55ae4e3cee5 /dotnet/Qpid.Client/Client/AMQConnection.cs
parenta204a5602d5c8569a3046d424d7d3dc506fcec22 (diff)
downloadqpid-python-c4fac88720bbfbaacbd821596d46e8715a161639.tar.gz
Locked on FailoverMutex where necessary.
Noted that AMQConnection.CloseSession and BasicMessageConsumer.Close both lock on FailoverMutex but do ProtocolWriter.SyncWrite which probably means that they need to do the FailoverSupport thing instead. If it's a problem, it exists also in the Java client. git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk/qpid@480190 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'dotnet/Qpid.Client/Client/AMQConnection.cs')
-rw-r--r--dotnet/Qpid.Client/Client/AMQConnection.cs1
1 files changed, 1 insertions, 0 deletions
diff --git a/dotnet/Qpid.Client/Client/AMQConnection.cs b/dotnet/Qpid.Client/Client/AMQConnection.cs
index ed85ec483b..a0ca8b7bcf 100644
--- a/dotnet/Qpid.Client/Client/AMQConnection.cs
+++ b/dotnet/Qpid.Client/Client/AMQConnection.cs
@@ -343,6 +343,7 @@ namespace Qpid.Client
public void CloseSession(AmqChannel channel)
{
+ // FIXME: Don't we need FailoverSupport here (as we have SyncWrite).
_protocolSession.CloseSession(channel);
AMQFrame frame = ChannelCloseBody.CreateAMQFrame(