[
https://issues.apache.org/jira/browse/DISPATCH-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16800716#comment-16800716
]
Ganesh Murthy commented on DISPATCH-1274:
-----------------------------------------
The following is a comment from [~gsim]
"This is a deadlock in the timer systems caused by DISPATCH-1274. That
optimisation assumes there will never be more than 256 timers. However
if initialHandshakeTimeoutSeconds is set on a listener, there will be a
timer created for every connection.
I'd suggest perhaps we consider backing out DISPATCH-1274 for now as it
an optimisation rather than a crucial feature or fix."
> Optimize qd_timer_schedule(0)
> ------------------------------
>
> Key: DISPATCH-1274
> URL: https://issues.apache.org/jira/browse/DISPATCH-1274
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Affects Versions: 1.5.0
> Reporter: Alan Conway
> Assignee: Alan Conway
> Priority: Major
> Fix For: 1.6.0
>
>
> qd_timer_schedule() uses the general timeout mechanisms which includes
> checking system time (on schedule and on PN_PROACTOR_TIMEOUT wakeup) and
> adding/removing work items from sorted list. Optimize the schedule(0) case as
> a simple work_list using pn_proactor_interrupt() for wakeups.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
