No subject

broker to run in the same Erlang VM. If that is the case then don't
start another VM for the client. If you want multiple Erlang VMs on the
same host then make sure you don't start full brokers with clashing node
names and listening ports on more than one of them.

Here is a sample transcript that demonstrates what you probably want:

$ rabbitmq-plugins enable amqp_client
The following plugins have been enabled:
  amqp_client

Plugin configuration has changed. Restart RabbitMQ for changes to take
effect.

(restart broker and connect an Erlang shell)

> rr(amqp_connection).
['P_access','P_basic','P_channel','P_confirm',
 'P_connection','P_dtx','P_exchange','P_file','P_queue',
 'P_stream','P_test','P_tunnel','P_tx','access.request',
 'access.request_ok',adapter_info,amqp_error,amqp_msg,
 amqp_params_direct,amqp_params_network,amqqueue,'basic.ack',
 'basic.cancel','basic.cancel_ok','basic.consume',
 'basic.consume_ok','basic.deliver','basic.get',
 'basic.get_empty'|...]

>{ok, Connection} = amqp_connection:start(#amqp_params_direct{}).
{ok,<0.227.0>}







-Emile