[
https://issues.apache.org/jira/browse/DISPATCH-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007671#comment-16007671
]
Jiri Danek commented on DISPATCH-390:
-------------------------------------
Here is backtrace for one of the other errors, since I've already started
posting these. The "exp_count >= pt->skip_count" failed assert appears rather
infrequently, I saw it only hapen twice:
/main/qpid-dispatch/build/tests/system_test.dir/system_tests_sasl_plain/RouterTestPlainSasl/setUpClass/core:
{noformat}
gdb) thread apply all bt
Thread 2 (Thread 0x7f19dbfb2700 (LWP 1261)):
#0 pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1 0x00007f19dfb0e9c0 in sys_cond_wait (cond=0x55690ee66300,
held_mutex=0x55690ee663c0) at /main/qpid-dispatch/src/posix/threading.c:91
#2 0x00007f19dfb240fa in router_core_thread (arg=0x55690ee65ff0) at
/main/qpid-dispatch/src/router_core/router_core_thread.c:53
#3 0x00007f19df472494 in start_thread (arg=0x7f19dbfb2700) at
pthread_create.c:333
#4 0x00007f19de81793f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:97
Thread 1 (Thread 0x7f19dff62080 (LWP 1259)):
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x00007f19de7633fa in __GI_abort () at abort.c:89
#2 0x00007f19de75ae37 in __assert_fail_base (fmt=<optimized out>,
assertion=assertion@entry=0x7f19df68f999 "exp_count >= pt->skip_count",
file=file@entry=0x7f19df68f910
"/main/qpid-proton/proton-c/src/proactor/epoll.c",
line=line@entry=172, function=function@entry=0x7f19df68fbd0
<__PRETTY_FUNCTION__.7045> "ptimer_callback") at assert.c:92
#3 0x00007f19de75aee2 in __GI___assert_fail (assertion=0x7f19df68f999
"exp_count >= pt->skip_count", file=0x7f19df68f910
"/main/qpid-proton/proton-c/src/proactor/epoll.c", line=172,
function=0x7f19df68fbd0 <__PRETTY_FUNCTION__.7045> "ptimer_callback") at
assert.c:101
#4 0x00007f19df68b578 in ptimer_callback (pt=0x55690edef5c8) at
/main/qpid-proton/proton-c/src/proactor/epoll.c:172
#5 0x00007f19df68e988 in proactor_process (p=0x55690edef550, timeout=true) at
/main/qpid-proton/proton-c/src/proactor/epoll.c:1514
#6 0x00007f19df68ee88 in proactor_do_epoll (p=0x55690edef550, can_block=true)
at /main/qpid-proton/proton-c/src/proactor/epoll.c:1634
#7 0x00007f19df68ef70 in pn_proactor_wait (p=0x55690edef550) at
/main/qpid-proton/proton-c/src/proactor/epoll.c:1657
#8 0x00007f19dfb30e4d in thread_run (arg=0x55690edfc150) at
/main/qpid-dispatch/src/server.c:817
#9 0x00007f19dfb3195a in qd_server_run (qd=0x55690eb64010) at
/main/qpid-dispatch/src/server.c:1031
#10 0x000055690e2478d0 in ?? ()
#11 0x000055690e24825b in main ()
{noformat}
> New pn_proactor-based IO driver
> -------------------------------
>
> Key: DISPATCH-390
> URL: https://issues.apache.org/jira/browse/DISPATCH-390
> Project: Qpid Dispatch
> Issue Type: New Feature
> Components: Container
> Affects Versions: 0.6.0
> Reporter: Alan Conway
> Assignee: Alan Conway
> Fix For: 1.0.0
>
>
> Replace the current proton IO driver with a driver based on the pn_proactor
> API. This will allow drop-in replacement of the IO layer for different
> platforms.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
