[
https://issues.apache.org/jira/browse/QPID-6152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14171116#comment-14171116
]
ASF subversion and git services commented on QPID-6152:
-------------------------------------------------------
Commit 1631810 from [~k-wall] in branch 'qpid/trunk'
[ https://svn.apache.org/r1631810 ]
QPID-6152: [Java Client] Allow connection/session close time to be overridden
by system property.
Change implementation so that the timeout is applied individually to each
session close, the connection and
the shutdown of the task pool. Also moved the shutdown of the task pool to a
finally, so that it occurs
even if one or more sessions fail to close.
> Connection close timeout too short when connections have many sessions
> ----------------------------------------------------------------------
>
> Key: QPID-6152
> URL: https://issues.apache.org/jira/browse/QPID-6152
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.30
> Reporter: Keith Wall
> Fix For: 0.31
>
>
> QPID-6037 reduced the timeout used when awaiting a connection (and its
> underlying sessions and task pool) from 20 second to 2 seconds. This causes
> a problem for connections with many sessions (we are seeing problems with 80
> sessions per connection).
> It would be better if the value were configurable, and the timeout applied to
> each part of the close operation individually, rather than the time available
> for each part decreased.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
