[
https://issues.apache.org/jira/browse/QPID-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286501#comment-13286501
]
Rob Godfrey commented on QPID-4033:
-----------------------------------
I guess it really depends where we thinkn this will be most useful... If you
have full debug logs then just the numbers are fine... if you are trying to do
any sort of post incident analysis based on just an exception stack trace in
the log, then having all the information available to you is pretty invaluable.
Accept that the length might be an issue though I would think that
Disp-127.0.0.1:1234/192.168.1.1:5672[1] would be short enough.
Accept the point about failover
> 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
> Assignee: 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: [email protected]
For additional commands, e-mail: [email protected]
