[
https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15299332#comment-15299332
]
Ted Ross commented on DISPATCH-343:
-----------------------------------
Vishal,
Can you check the integrity of your build? Make sure that the dispatch and
proton libraries that you're running with are the same as you built with. You
can run ldd against the qdrouterd executable to get the list of libraries.
The type of problems you are reporting look like internal data corruption.
Nobody else has reported seeing this and our testing has not shown any similar
behavior. I'm wondering if there's something wrong with your installation or
if there's something specific to Debian going on.
We are putting together a Debian 8 system to test your scenario on.
-Ted
> Router stops accepting connections after load from parallel senders
> -------------------------------------------------------------------
>
> Key: DISPATCH-343
> URL: https://issues.apache.org/jira/browse/DISPATCH-343
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
> Affects Versions: 0.6.0
> Reporter: Vishal Sharda
> Priority: Blocker
> Attachments: Connection_aborted.png, Connection_aborted_1.png,
> Crash.png, Crash_10S_2R.png, R1.conf, R2.conf, R3.conf,
> Sender_router_crash.png, bt_qd_dealloc.png, bt_qdr_link_cleanup_CT.png,
> bt_sasl.png, bt_sys_mutex_lock.png, config1_nossl.conf, config2_nossl.conf,
> resource-limit-exceeded.png
>
>
> We ran 2 parallel senders and 2 receivers with each sender sending 50000
> messages. After a while we saw that router stopped accepting connections
> even from qdstat. We saw various errors in the logs (screenshots attached).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
