QPid Client V0.32 causes RabbitMQ 3.5 to crash (in the log)

[Kai Hackemesser]

Hello,

I try to create a durable JMS topic subscription to a RabbitMQ V3.5 server using Qpid-client V0.32 library. On my client side I receive an exception:

17:04:42 INFO  Connection exception caught therefore going to attempt failover: java.net.SocketException: Connection reset

java.net.SocketException: Connection reset

at java.net.SocketInputStream.read(SocketInputStream.java:196)

at java.net.SocketInputStream.read(SocketInputStream.java:122)

at org.apache.qpid.transport.network.io.IoReceiver.run(IoReceiver.java:156)

at java.lang.Thread.run(Thread.java:745)

17:04:42 INFO  No Waiters for error. Saving as last error:Exception thrown against AMQConnection:

Host: functional

Port: 5672

Virtual Host: 

Client ID: KaiH.sqr2eqa

Active session count: 1: org.apache.qpid.AMQDisconnectedException: Server closed connection and reconnection not permitted.

And on the RabbitMQ log I see:

=CRASH REPORT==== 18-Jun-2015::17:04:20 ===

  crasher:

    initial call: rabbit_reader:init/2

    pid: <0.1739.7>

    registered_name: []

    exception exit: {unknown_method_id,{40,22}}

      in function  rabbit_framing_amqp_0_9_1:lookup_method_name/1 

      in call from rabbit_command_assembler:analyze_frame/3 

      in call from rabbit_reader:handle_frame/4 

      in call from rabbit_reader:handle_input/3 

      in call from rabbit_reader:recvloop/4 

      in call from rabbit_reader:run/1 

      in call from rabbit_reader:start_connection/5 

    ancestors: [<0.1737.7>,rabbit_tcp_client_sup,rabbit_sup,<0.146.0>]

    messages: [{'EXIT',#Port<0.116904>,normal}]

    links: [<0.1737.7>]

    dictionary: [{{channel,1},

                   {<0.1747.7>,{method,rabbit_framing_amqp_0_9_1}}},

                  {process_name,

                      {rabbit_reader,

                          <<"172.25.1.85:60293 -> 172.16.1.169:5672">>}},

                  {{ch_pid,<0.1747.7>},{1,#Ref<0.0.15.8937>}}]

    trap_exit: true

    status: running

    heap_size: 2586

    stack_size: 27

    reductions: 3724

  neighbours:

What is wrong and can I do something against it? 

Or do you know a workaround to get a durable topic subscription endpoint in camel with RabbitMQ?

Cheers

Kai

[Michael Klishin]

The client uses a protocol method RabbitMQ doesn't know about, presumably an extension.

Our own JMS client should be open sourced in the upcoming months.

MK

> On 18/6/2015, at 8:29, Kai Hackemesser <kai.hac...@gmail.com> wrote:
>
> {unknown_method_id,{40,22}}