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

Lynton Grice lynton.grice at logosworld.com
Tue Jun 9 18:42:16 BST 2009


Hi Matthias,

 

I have tried to do what you asked for in order for you to understand the
problem better, forgive me if I misinterpreted one or two things, just let
me know and I will try again ;-)

 

I really appreciate the help, thank you.

 

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

      You can see the Rabbit* folders below...

 

cid:image001.png at 01C9E936.39031960

cid:image002.png at 01C9E936.39031960

cid:image003.png at 01C9E936.39031960

 

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

                Not sure how you wanted this represented?

 

cid:image004.png at 01C9E936.39031960

 

Just for interest this is the version etc of the Server....

cid:image005.png at 01C9E936.E23BB780

 

Here is the client.....latest version....

cid:image006.png at 01C9E936.E23BB780

 

 

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

 

cid:image007.png at 01C9E936.E23BB780

 

Here are my environment variables, not sure if you wanted to see them...

 

cid:image010.png at 01C9E937.54F671C0

 

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

NOTE: I *assume* that I don't need to add anything to the load path because
the server + client are in the Erlang LIB folder.....

Also, you can see it HANGING again.....

cid:image008.png at 01C9E938.2264EDD0

 

And just to see the LOG again from this evening...

 

=INFO REPORT==== 9-Jun-2009::19:13:10 ===

started TCP listener on 0.0.0.0:5672

 

=INFO REPORT==== 9-Jun-2009::19:22:59 ===

accepted TCP connection on 0.0.0.0:5672 from 127.0.0.1:1822

 

=INFO REPORT==== 9-Jun-2009::19:22:59 ===

starting TCP connection <0.148.0> from 127.0.0.1:1822

 

=ERROR REPORT==== 9-Jun-2009::19:23:09 ===

error on TCP connection <0.148.0> from 127.0.0.1:1822

{handshake_timeout,frame_header}

 

=INFO REPORT==== 9-Jun-2009::19:23:09 ===

closing TCP connection <0.148.0> from 127.0.0.1:1822

 

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

 

cid:image009.png at 01C9E938.2264EDD0

 

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

 

cid:image011.png at 01C9E938.2264EDD0

 

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

For this is am just calling the "lifecycle_test" function in the
"network_client_test.erl" script in the TESTS folder of the client code.....

 

-module(network_client_test).

 

-export([test_coverage/0]).

 

-include_lib("eunit/include/eunit.hrl").

 

basic_get_test() ->

    test_util:basic_get_test(new_connection()).

 

basic_return_test() ->

    test_util:basic_return_test(new_connection()).

 

basic_qos_test() ->

    test_util:basic_qos_test(new_connection()).

 

basic_recover_test() -> 

    test_util:basic_recover_test(new_connection()).

 

basic_consume_test() -> 

    test_util:basic_consume_test(new_connection()).

 

lifecycle_test() ->

    test_util:lifecycle_test(new_connection()).

 

basic_ack_test() ->

    test_util:basic_ack_test(new_connection()).

 

channel_lifecycle_test() ->

    test_util:channel_lifecycle_test(new_connection()).

 

queue_unbind_test() ->

    test_util:queue_unbind_test(new_connection()).

 

command_serialization_test() ->

    test_util:command_serialization_test(new_connection()).

 

teardown_test() ->

    test_util:teardown_test(new_connection()).

 

rpc_test() ->

    test_util:rpc_test(new_connection()).

 

%%--------------------------------------------------------------------------
-

%% Negative Tests

 

non_existent_exchange_test() -> 

  negative_test_util:non_existent_exchange_test(new_connection()).

 

hard_error_test() ->

    negative_test_util:hard_error_test(new_connection()).

 

%%--------------------------------------------------------------------------
-

%% Common Functions

 

new_connection() ->

  amqp_connection:start("guest", "guest", "localhost").

 

test_coverage() ->

    rabbit_misc:enable_cover(),

    test(),

    rabbit_misc:report_cover().

 

 

 

 

 

 

 

 

 

-----Original Message-----
From: Matthias Radestock [mailto:matthias at lshift.net] 
Sent: 09 June 2009 04:52 PM
To: Lynton Grice
Cc: rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] Erlang RabbitMQ Client hanshake problem on
"State = Driver:handshake(InitialState), "

 

Lynton,

 

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 0.0.0.0:5672 from 127.0.0.1:1319

> 

> =INFO REPORT==== 9-Jun-2009::14:23:53 ===

> starting TCP connection <0.175.0> from 127.0.0.1:1319

> 

> =ERROR REPORT==== 9-Jun-2009::14:24:01 ===

> error on TCP connection <0.175.0> from 127.0.0.1:1319

> connection_closed_abruptly

> 

> =INFO REPORT==== 9-Jun-2009::14:24:01 ===

> closing TCP connection <0.175.0> from 127.0.0.1:1319

 

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 ;)

 

 

Regards,

 

Matthias.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090609/d5273bd8/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 11127 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090609/d5273bd8/attachment.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 9455 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090609/d5273bd8/attachment-0001.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 5719 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090609/d5273bd8/attachment-0002.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 5413 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090609/d5273bd8/attachment-0003.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 7932 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090609/d5273bd8/attachment-0004.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 11551 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090609/d5273bd8/attachment-0005.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 10750 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090609/d5273bd8/attachment-0006.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 33980 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090609/d5273bd8/attachment-0007.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 2993 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090609/d5273bd8/attachment-0008.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 4289 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090609/d5273bd8/attachment-0009.png 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 5227 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090609/d5273bd8/attachment-0010.png 


More information about the rabbitmq-discuss mailing list