jbrisbin / amqp_client

Rebar-friendly fork of rabbitmq-erlang-client
101 stars 118 forks source link

amqp_channel_sup crashed after bad request in channel #17

Open Prots opened 10 years ago

Prots commented 10 years ago

amqp_channel_sup crashed after bad request in channel and didn't start new child. The problem arise when I try to make a bad request in channel, for example, publish string message instead of binary.

ERROR message:

[error] Error in process <0.138.0> on node 'dev@prots' with exit value: {badarg,[{erlang,size,"t",[]},{rabbit_binary_generator,build_content_frames,7,[{file,"src/rabbit_binary_generator.erl"},{line,98}]},{rabbit_binary_generator,build_simple_content_frames,4,[{file,"src/rabbit_binary_ge...

18:36:56.194 [error] Supervisor {<0.135.0>,amqp_channel_sup} had child writer started with rabbit_writer:start_link(#Port<0.4123>, 2, 131072, rabbit_framing_amqp_0_9_1, <0.137.0>, {<<"client 10.21.2.166:34725 -> 10.56.128.24:5672">>,2}) at <0.138.0> exit with reason bad argument in call to erlang:size(116) in rabbit_binary_generator:build_content_frames/7 line 98 in context child_terminated 18:36:56.194 [error] Supervisor {<0.135.0>,amqp_channel_sup} had child writer started with rabbit_writer:start_link(#Port<0.4123>, 2, 131072, rabbit_framing_amqp_0_9_1, <0.137.0>, {<<"client 10.21.2.166:34725 -> 10.56.128.24:5672">>,2}) at <0.138.0> exit with reason reached_max_restart_intensity in context shutdown