<div>Hi Jerry,</div>
<div>�</div>
<div>you found the same pdf that I did. </div>
<div>�</div>
<div>I'm not knowingly using RPC continuation at this stage, unless using the Subscription pattern falls under this category. Also, I am careful to use a different channel for each subscription or basic channe that lives�on the same thread.�</div>
<div>�</div>
<div>Would you like me to get in touch if I can repeat the error with a test case?� </div>
<div>�</div>
<div>-Steven<br><br></div>
<div class="gmail_quote">On 15 December 2010 16:56, Jerry Kuch <span dir="ltr"><<a href="mailto:jerryk@vmware.com">jerryk@vmware.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">Steven: �Is there any chance that the channel instance on which you're doing this work is being used by more than one thread?<br>
<br>In the .NET client one expects this error when something tries to queue up more than one RPC continuation in the internal continuation queue at a time. �The Rabbit .NET client user guide talks about such thread safety issues:<br>
<div class="im"><br><a href="http://www.rabbitmq.com/releases/rabbitmq-dotnet-client/v1.5.0/rabbitmq-dotnet-client-1.5.0-user-guide.pdf" target="_blank">http://www.rabbitmq.com/releases/rabbitmq-dotnet-client/v1.5.0/rabbitmq-dotnet-client-1.5.0-user-guide.pdf</a><br>
<br></div>in some detail in a couple of spots.<br><br>The Rabbit Java client has similar restrictions. �With both the Java and .NET clients, it makes sense to structure your application so that a unique thread owns a given instance of a non-thread safe Rabbit client resource (e.g. Channels in the Java client, IModel in the .NET).<br>
<br>Best regards,<br>Jerry<br>
<div>
<div></div>
<div class="h5"><br>On Dec 15, 2010, at 8:28 AM, Steven Taylor wrote:<br><br>Hi,<br><br>Got this error: "Pipelining of requests forbidden"<br><br>Found a reference in the documentation (see below). �As part of the "I assert queue exists" logic, I was (re-)declaring the exhange. �Is that wrong?<br>
<br>Could it be a threading issue?<br><br><a href="http://www.rabbitmq.com/releases/rabbitmq-dotnet-client/v1.5.0/rabbitmq-dotnet-client-1.5.0-user-guide.pdf" target="_blank">http://www.rabbitmq.com/releases/rabbitmq-dotnet-client/v1.5.0/rabbitmq-dotnet-client-1.5.0-user-guide.pdf</a><br>
<br>NotSupportedException<br><br>s being thrown from a method in class RpcContinuationQueue<br><br>complaining about<br><br>"Pipelining of requests forbidden" (which occurs in situations where<br><br>more than one AMQP RPC, such as<br>
<br>ExchangeDeclare, is run simultaneously).<br><br>Offending Line:<br>BasicGetResult msg=ch.BasicGet(QueueNme,false);<br><br>thanks,<br>-Steven<br></div></div><ATT00001..txt><br><br></blockquote></div><br>