[
https://issues.apache.org/jira/browse/DISPATCH-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712175#comment-15712175
]
Paolo Patierno edited comment on DISPATCH-583 at 12/1/16 2:53 PM:
------------------------------------------------------------------
Ok ... I'm quite sure that the segmentation fault is related to connection
suddenly closed. I have a systematic way for crashing, using my mqtt-frontend
project and running this specific test :
mvn -Dtest=PublishTest#publishQoS0toMqtt test
I have to fix synchronization in my unit test to avoid this suddenly connection
close but now we have more info to discover why the router crash.
was (Author: ppatierno):
Ok ... I'm quite sure that the segmentation fault is related to connection
suddenly closed. I have a systematic way for crashing, using my mqtt-frontend
project and running this specific test :
mvn -Dtest=PublishTest#publishQoS0toMqtt test
I have to fix synchronization in my unit test to avoid this seddenly connection
close but now we have more info to discover why the router crash.
> Random segmentation fault
> -------------------------
>
> Key: DISPATCH-583
> URL: https://issues.apache.org/jira/browse/DISPATCH-583
> Project: Qpid Dispatch
> Issue Type: Bug
> Affects Versions: 0.8.0
> Reporter: Paolo Patierno
> Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
> Attachments: qdrouterd.conf
>
>
> Hello,
> working with the following project :
> https://github.com/EnMasseProject/mqtt-frontend
> using the router, I have random "segmentation fault" errors when the
> SubscribeTest is executed. It happens running the test 3-4 times ... or 20
> times ... totally random.
> You can reproduce it, cloning the above repo and running :
> mvn -Dtest=SubscribeTest test
> I used the route built from the repo source code (about 2 weeks ago) but
> applying the patch for message annotations on that.
> I got the backtrace of one of the crash :
> #0 0x0000000f00747369 in ?? ()
> #1 0x00007f0eceddcf69 in pn_class_equals (clazz=<optimized out>,
> a=<optimized out>, b=b@entry=0x7f0eb800bd90) at
> /qpid-proton-0.15.0/proton-c/src/object/object.c:169
> #2 0x00007f0eceddd466 in pn_list_index (list=list@entry=0x7f0eb802c0c0,
> value=value@entry=0x7f0eb800bd90) at
> /qpid-proton-0.15.0/proton-c/src/object/list.c:88
> #3 0x00007f0eceddd559 in pn_list_remove (list=0x7f0eb802c0c0,
> value=value@entry=0x7f0eb800bd90) at
> /qpid-proton-0.15.0/proton-c/src/object/list.c:99
> #4 0x00007f0ecede82ea in pn_link_finalize (object=0x7f0eb800bd90) at
> /qpid-proton-0.15.0/proton-c/src/engine/engine.c:1129
> #5 0x00007f0eceddce19 in pn_class_decref (clazz=0x7f0ecf013480 <clazz>,
> object=0x7f0eb800bd90) at /qpid-proton-0.15.0/proton-c/src/object/object.c:95
> #6 0x00007f0ecedeadb0 in pn_event_finalize (event=0x7f0eb802a580) at
> /qpid-proton-0.15.0/proton-c/src/events/event.c:212
> #7 pn_event_finalize_cast (object=0x7f0eb802a580) at
> /qpid-proton-0.15.0/proton-c/src/events/event.c:257
> #8 0x00007f0eceddce19 in pn_class_decref (clazz=0x7f0ecf013600 <clazz>,
> clazz@entry=0x7f0ecf012f00 <PN_OBJECT>, object=0x7f0eb802a580) at
> /qpid-proton-0.15.0/proton-c/src/object/object.c:95
> #9 0x00007f0eceddd02f in pn_decref (object=<optimized out>) at
> /qpid-proton-0.15.0/proton-c/src/object/object.c:253
> #10 0x00007f0ecedeb0a2 in pn_collector_pop
> (collector=collector@entry=0x7f0eb8036450) at
> /qpid-proton-0.15.0/proton-c/src/events/event.c:189
> #11 0x00007f0ecf055d43 in process_connector (cxtr=0x7f0eb8002f90,
> qd_server=0x2517e70) at /qpid-dispatch/src/server.c:851
> #12 thread_run (arg=<optimized out>) at /qpid-dispatch/src/server.c:1075
> #13 0x00007f0ecebb45ba in start_thread () from /lib64/libpthread.so.0
> #14 0x00007f0ece1037cd in clone () from /lib64/libc.so.6
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
