activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-1520) Add connectionID to trace logging that deals with packet reading/writing
Date Tue, 28 Nov 2017 20:58:00 GMT

    [ https://issues.apache.org/jira/browse/ARTEMIS-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269444#comment-16269444
] 

ASF GitHub Bot commented on ARTEMIS-1520:
-----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/activemq-artemis/pull/1665


> Add connectionID to trace logging that deals with packet reading/writing 
> -------------------------------------------------------------------------
>
>                 Key: ARTEMIS-1520
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1520
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 2.4.0
>            Reporter: Pat Fox
>            Priority: Minor
>
> There is some very good logging for tracking packet read/write operations in 
> org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl and org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl
.However it is difficult to distinguish which TCP connection a packet arrived on or was written
to. 
> It would be good to add a connection ID to that logging so it is easier to track the
packet flow on an individual connection.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message