<br><div class="gmail_quote"><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>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></blockquote><div>Is this valid also when running rabbitmq erlang client and rabbitmq server on separate erlang nodes?<br><br>I sent 3 amqp message to the rabbitmq broker from a separate erlang client node. The three 3 amqp messages create 3 rabbit_writer:mainloop/1 processes. This rabbit_writer:mainloop/1 process never goes away.<br>
<br><0.71.0> rabbit_writer:mainloop/1 233 132 0<br> rabbit_writer:mainloop/1 2 <br><0.72.0> rabbit_writer:mainloop/1 233 132 0<br>
rabbit_writer:mainloop/1 2 <br><0.73.0> rabbit_writer:mainloop/1 233 132 0<br> rabbit_writer:mainloop/1 2 <br>
<br>One rabbit_writer:mainloop process traced:<br><br>initial_call: rabbit_writer:mainloop/1<br>current_function: rabbit_writer:mainloop/1<br>heap_size: 233<br>stack_size: 2<br>reductions: 132<br>trap_exit: false<br><0.72.0>: getting_linked <0.112.0><br>
<br>After that I increased number of processes on a single erlang node to something higer than 50 000 and sent 50 000 messages. For some reason, 50 000 rabbit_writer:mainloop processes are still there. They don't go away. Processes only go away when I restart the rabbit erlang client node.<br>
<br>7> erlang:system_info(process_count).<br>50044<br> <br>Thank you,<br>Joe<br></div></div>