[rabbitmq-discuss] Erlang RabbitMQ Client hanshake problem on "State = Driver:handshake(InitialState), "

Matthias Radestock matthias at lshift.net
Tue Jun 9 15:52:20 BST 2009


Lynton Grice wrote:
> Hi Matthias,
> I have been looking through the posts and cannot see anything specific that
> says exactly how to solve this issue. Yes, you mention load path etc....so I
> assume "erl -pa" etc.....but can I see an example of what needs to be done
> "load path" wise for the client to work? I have been trying to get the
> client to work to almost 2 days now....;-(
> I have installed BOTH the server and client folders into the
> %ERLANG_HOME%\erl5.7.1\lib folder....surely that should be fine?

If you have the server in the above dir, as per the installation
instructions, then the client code should find the server libraries
without needing to modify the load path.

In order to diagnose this further, please send me

1) a directory listing of %ERLANG_HOME%\erl5.7.1\lib

2) a deep directory listing for all rabbitmq* directories in the above.

3) the location of the erlang client directory, and a deep directory
listing thereof

4) the exact command line used for invoking the erlang client, including
the dir it is run from

5) the output of [P || P <- code:get_path(), string:str(P, "rabbit") =/=
0]. when run inside the Erlang client's shell.

6) the output of  [code:which(M) || M <- [lib_amqp,
rabbit_framing_channel, rabbit]]. when run inside the Erlang client's shell.

7) the sequence of erlang function calls used in the test

> I just keep getting this:
> =INFO REPORT==== 9-Jun-2009::14:23:53 ===
> accepted TCP connection on from
> =INFO REPORT==== 9-Jun-2009::14:23:53 ===
> starting TCP connection <0.175.0> from
> =ERROR REPORT==== 9-Jun-2009::14:24:01 ===
> error on TCP connection <0.175.0> from
> connection_closed_abruptly
> =INFO REPORT==== 9-Jun-2009::14:24:01 ===
> closing TCP connection <0.175.0> from

Are you still getting {undef, [{rabbit_framing_channel,start_link,...}]}
error in the client? If so then the above is likely a consequence of that.

> Yes, I do agree I probably need to understand Erlang better with regard to
> the "load path" etc....

Some knowledge of Erlang when using the Erlang client is highly
recommended ;)



More information about the rabbitmq-discuss mailing list