[
https://issues.apache.org/jira/browse/DISPATCH-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15307623#comment-15307623
]
Ted Ross commented on DISPATCH-343:
-----------------------------------
Quick status on this issue:
The thing about this test that causes the problem is that it uses 2-ack
transfers. The messages are sent by the sender, acknowledged (but not settled)
by the receiver, then settled by the sender. However, since it is built on
Messenger with a limited windows size, sometimes the receiver will settle the
deliveries (presumably because the window is full). All of this should work
fine of course, but it exposes a bug in the lifecycle management of deliveries
in Dispatch Router. A fix for this is imminent.
If this is a blocker for your project, you can probably work around it by
switching away from 2-ack deliveries. They are probably not providing any
added value since Messenger doesn't support exactly-once delivery.
> 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
> Assignee: Ted Ross
> Priority: Blocker
> Fix For: 0.6.0
>
> 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,
> drivers.tar.gz, 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]