<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Joe,<div><br></div><div>A cursory glance indicates that you are using the wrong routing key to publish to the exchange.</div><div><br></div><div>If you use a.b.c.d instead of a.b.c.*, then when a queue binds itself to a.b.c.*, messages will be delivered to it.</div><div><br></div><div>Hence why you are getting a get_empty.</div><div><br></div><div>So just change the routing key in the amqp_async_pub module.</div><div><br></div><div>As for the errors you are seeing, the reason is because you are passing in integers as the publish payload.</div><div><br></div><div>The API however, expects payload fragments to be opaque binaries rather than any Erlang type.</div><div><br></div><div>So to fix this problem, just convert whatever payload fragment you want to send to a binary.</div><div><br></div><div>In your case you are sending integers, so you could pass in something like <<MyInteger:32>> instead of MyInteger.</div><div><br></div><div>This may be a question for the design of the API. It may well be worthwile performing a guard condition (i.e. is_binary(Payload)) on the submission of a message. I'll look into this.</div><div><br></div><div>BTW, if you don't supply a host name when starting the connection, the client will start in a direct mode using native Erlang message passing rather than AMQP wire framing. This means that the client and server run in the same interpreter and eliminate the network overhead.</div><div><br></div><div>HTH,</div><div><br></div><div>Ben</div><div><br><div><html>On 14 Apr 2008, at 18:59, Joe Lee wrote:</html><br class="Apple-interchange-newline"><blockquote type="cite">Here are the files. I think problem maybe how the Payload in amqp_async_pub is assigned setup. I maybe wrong.<br><br>Joe<br><br><div class="gmail_quote">On Mon, Apr 14, 2008 at 11:39 AM, Ben Hood <<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</a>> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div>Hi Joe,</div><div><br></div><div>Could you send the complete source code of the test that causes these problems so that we can have a look at this, please?</div> <div><br></div><div>Thx,</div><div><br></div><div>Ben</div><br><div><div><div></div><div class="Wj3C7c">On 14 Apr 2008, at 16:20, Joe Lee wrote:<br></div></div><blockquote type="cite"><div><div></div><div class="Wj3C7c">I tried to send messages sequentially to a single rabbitmq server running on <a href="http://127.0.0.1" target="_blank">127.0.0.1</a>. After sending messages around 32000, erlang client node publishing the message crashed. When I looked at the crash dump, I see close to 32767 rabbit_writer:mainloop/1 process still in waiting status. I am not sure why so many rabbit_writer:mainloop processes are still hanging around. Furthermore, I started another node to get published message from rabbitmq server, rabbitmq server sends basic.get_empty. <br> <br>crash_dump.erl says: <br>Maximum number of Erlang Process has reached 32768<br><br>Process status in erlang crash dump:<br><br><0.32765.6> rabbit_writer:mainloop/1 Waiting 136 233 0<br><0.32766.13> rabbit_writer:mainloop/1 Waiting 132 233 0<br> <0.32767.1> rabbit_writer:mainloop/1 Waiting 136 233 0<br><br><br>I tried spawning 3 erlang processes simultaneously to publish message using pmap to a single rabbitmq_server running on <a href="http://127.0.0.1" target="_blank">127.0.0.1</a> and rabbitmq server throws badarg error. Here is the error below:<br> <br>=ERROR REPORT==== 14-Apr-2008::19:43:23 ===<br>Error in process <0.68.0> on node 'test@home' with exit value: {badarg,[{erlang,size,[1]},{rabbit_binary_generator,build_content_frames,5},{rabbit_binary_generator,build_simple_content_frames,3},{rabbit_writer,assemble_frames,4},{rabbit_writer,internal_send_command_async... <br> <br><br>=ERROR REPORT==== 14-Apr-2008::19:43:23 ===<br>Error in process <0.70.0> on node 'test@home' with exit value: {badarg,[{erlang,size,[3]},{rabbit_binary_generator,build_content_frames,5},{rabbit_binary_generator,build_simple_content_frames,3},{rabbit_writer,assemble_frames,4},{rabbit_writer,internal_send_command_async... <br> <br><br>=ERROR REPORT==== 14-Apr-2008::19:43:23 ===<br>Error in process <0.69.0> on node 'test@home' with exit value: {badarg,[{erlang,size,[2]},{rabbit_binary_generator,build_content_frames,5},{rabbit_binary_generator,build_simple_content_frames,3},{rabbit_writer,assemble_frames,4},{rabbit_writer,internal_send_command_async... <br> <br>Have a look into this one: closed<br>Have a look into this one: closed<br>Have a look into this one: closed<br>(test@home)2> <br><br>I am not sure what these errors mean. Can someone tell me what I am doing wrong?<br> <br>Thank you,<br>Joe<br></div></div> _______________________________________________<br>rabbitmq-discuss mailing list<br><a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br> <a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br></blockquote></div><br></div><br>_______________________________________________<br> rabbitmq-discuss mailing list<br> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br> <a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br> <br></blockquote></div><br> <span><amqp_async_consume.erl></span><span><amqp_async_pub.erl></span><span><my_pmap.erl></span><span><rabbit_test.erl></span></blockquote></div><br></div></body></html>