[
https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300052#comment-15300052
]
Ulf Lilleengen edited comment on DISPATCH-343 at 5/25/16 1:43 PM:
------------------------------------------------------------------
Vishal,
If you have not already done so, it might be an idea to check /var/log/mcelog
for hardware issues as well. Not sure if it exists on debian.
was (Author: lulf):
Vishal,
If you have not already done so, it might be an idea to check /var/log/mcelog
for hardware issues as well.
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
