You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <ji...@apache.org> on 2012/05/31 12:35:23 UTC
[jira] [Commented] (QPID-4033) add a connection id to the session
dispatcher thread name to avoid name overloading
[ https://issues.apache.org/jira/browse/QPID-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286465#comment-13286465 ]
Rob Godfrey commented on QPID-4033:
-----------------------------------
By connection-id do you mean the remote IP addr/hostname and port, and local port?
The string "Channel" also seems redundant in the name
> add a connection id to the session dispatcher thread name to avoid name overloading
> -----------------------------------------------------------------------------------
>
> Key: QPID-4033
> URL: https://issues.apache.org/jira/browse/QPID-4033
> Project: Qpid
> Issue Type: Improvement
> Components: Java Client
> Reporter: Robbie Gemmell
> Priority: Minor
> Fix For: 0.17
>
>
> The session dispatcher thread is currently called "Dispatcher-Channel-<channel number>", this leads to name overloading if there is mroe than one connection present as the channel numbers are not unique on each connection. We should add a connection id number to allow differentiating the names of dispatcher threads on different connections.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org