qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "michael goulish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (PROTON-566) crash in pn_transport_set_max_frame
Date Wed, 16 Apr 2014 18:46:18 GMT

     [ https://issues.apache.org/jira/browse/PROTON-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

michael goulish closed PROTON-566.
----------------------------------

    Resolution: Fixed

It looks like this is not a proton issue, but a dispatch issue.
I'm closing this and moving it.

> crash in pn_transport_set_max_frame
> -----------------------------------
>
>                 Key: PROTON-566
>                 URL: https://issues.apache.org/jira/browse/PROTON-566
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.7
>         Environment: 3 boxes.  1 with senders, 1 with receivers, and 1 in the middle
with a single router.
>            Reporter: michael goulish
>
> Here's what I do:
> ( I have saved all relevant software so I can repro this. )
>   1. On router box, start 1 router.
>   2. On receiver box, start 1000 receivers.  With delays in between each group of 50,
so as to avoid backlog problem.
>   3. After receivers are all started, start 1000 senders also with delays.
>      Senders start up but do not yet begin sending until I manually "signal" them by
touching a file.
>   4. Short time after sender start sending, qdrouter crashes in proton code, with this
traceback:
>   Core was generated by `/home/mick/dispatch/build/router/qdrouterd --config ./config_1/X.conf'.
>   Program terminated with signal 11, Segmentation fault.
>   #0  0x00007f29d3c0f3c0 in pn_transport_set_max_frame (transport=0x0, size=65536)
>       at /home/mick/proton/proton-c/src/transport/transport.c:1915
>       1915        transport->local_max_frame = size;
>       
>   #0  0x00007f8ad5a613c0 in pn_transport_set_max_frame (transport=0x0, size=65536)
>       at /home/mick/proton/proton-c/src/transport/transport.c:1915
>       #1  0x00007f8ad5cdd4bd in thread_process_listeners (qd_server=0x14f8e10) at /home/mick/dispatch/src/server.c:100
>       #2  0x00007f8ad5cddedb in thread_run (arg=0x1490bf0) at /home/mick/dispatch/src/server.c:416
>       #3  0x0000003638c07de3 in start_thread () from /lib64/libpthread.so.0
>       #4  0x00000036388f616d in clone () from /lib64/libc.so.6
> Looks like this is not a proton problem, but something in dispatch.
> I'm closing this and moving it....



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message