Uploaded image for project: 'Qpid Dispatch'
  1. Qpid Dispatch
  2. DISPATCH-865

Segmentation fault while running 2-node Artemis tests

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • 1.0.0
    • 1.0.0
    • Router Node
    • None

    Description

      While running qpid-interop-test against a 2-node + broker configuration, node 2 fails with a segmentation fault. The configuration is as follows:

              9001           5672           5672            9002
      Sender -------> Node1 ------> Artemis ------> Node 2 ------> Receiver
      

      The configuration files for nodes 1 and 2 are attached.
      The client is amqp_types_test from qpid-interop-test, and is run as follows:

      amqp_types_test.py --sender localhost:9001 --receiver localhost:9002
      Test Broker: qpid-dispatch-router v.1.0.0 on <platform not found>
      
      test_binary_ProtonCpp->ProtonCpp (__main__.BinaryTestCase) ... ok
      test_binary_ProtonCpp->ProtonPython (__main__.BinaryTestCase) ...
      

      which is where the test hangs, and where node 2 fails. Using gdb, I see the following stacktrace:

      Thread 5 "qdrouterd" received signal SIGSEGV, Segmentation fault.
      [Switching to Thread 0x7fffe882e700 (LWP 16963)]
      0x00007ffff7bb6c8b in qdr_node_disconnect_deliveries (core=0x8fcec0, link=0x0, qdlv=qdlv@entry=0x7fffdc030610, pdlv=pdlv@entry=0x7fffd40008d0) at /home/kpvdr/RedHat/qpid-dispatch/src/router_node.c:76
      76	        DEQ_REMOVE(*list, ref);
      (gdb) bt
      #0  0x00007ffff7bb6c8b in qdr_node_disconnect_deliveries (core=0x8fcec0, link=0x0, qdlv=qdlv@entry=0x7fffdc030610, pdlv=pdlv@entry=0x7fffd40008d0)
          at /home/kpvdr/RedHat/qpid-dispatch/src/router_node.c:76
      #1  0x00007ffff7bb6fbf in CORE_delivery_update (context=0x89d570, dlv=0x7fffdc030610, disp=36, settled=<optimized out>) at /home/kpvdr/RedHat/qpid-dispatch/src/router_node.c:1435
      #2  0x00007ffff7baa255 in qdr_connection_process (conn=0x95f5d0) at /home/kpvdr/RedHat/qpid-dispatch/src/router_core/connections.c:316
      #3  0x00007ffff7b95668 in writable_handler (container=0x89d3d0, container=0x89d3d0, conn=0x7fffe000a360, qd_conn=0x7fffe0000b50) at /home/kpvdr/RedHat/qpid-dispatch/src/container.c:329
      #4  qd_container_handle_event (container=0x89d3d0, event=event@entry=0x7fffe002f3e0) at /home/kpvdr/RedHat/qpid-dispatch/src/container.c:552
      #5  0x00007ffff7bbb3b5 in handle (qd_server=qd_server@entry=0x883dc0, e=0x7fffe002f3e0) at /home/kpvdr/RedHat/qpid-dispatch/src/server.c:912
      #6  0x00007ffff7bbc0d8 in thread_run (arg=0x883dc0) at /home/kpvdr/RedHat/qpid-dispatch/src/server.c:930
      #7  0x00007ffff75185ca in start_thread (arg=0x7fffe882e700) at pthread_create.c:333
      #8  0x00007ffff67eb0cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
      

      and occurs 100% of the time.

      Qpid Dispatch version: master as of Nov 2, 2017

      Attachments

        1. qdrouterd.node2.conf
          2 kB
          Kim van der Riet
        2. qdrouterd.node1.conf
          2 kB
          Kim van der Riet

        Activity

          People

            tross Ted Ross
            kpvdr Kim van der Riet
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: