[rabbitmq-discuss] Using rabbitmq-http2 (was: simple.publish over the JSON RPC interface)

Nathan Gray n8gray at n8gray.org
Thu Aug 6 07:09:07 BST 2009

On Wed, Aug 5, 2009 at 10:53 PM, Nathan Gray<n8gray at n8gray.org> wrote:
> If I replace the call to poll with channel.declare, then a session
> timeout of 5s gives me the gen_server timeout error again.  If I set
> the session timeout to something less than 5s I get this response:
> {"version":"1.1","id":1,"error":{"name":"JSONRPCError","code":504,"message":"Closed","error":null}}
> And again, I'm not sure why it waits for the session timeout to expire
> before replying.

Ok, never mind.  I figured this one out myself.  I shouldn't have set
"nowait" to True.  It seems like "nowait" in a synchronous API should
return immediately but instead it never returns.  On a perhaps related
note, "cast" has the same strange behavior.  Cast methods like
"simple.publish" block until the session times out.  This seems very
odd to me.  Is there some rationale for this design that I'm not



More information about the rabbitmq-discuss mailing list