You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2018/01/22 18:28:01 UTC
[jira] [Resolved] (ARTEMIS-1520) Add connectionID to trace logging
that deals with packet reading/writing
[ https://issues.apache.org/jira/browse/ARTEMIS-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Bertram resolved ARTEMIS-1520.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.5.0
> 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
> Fix For: 2.5.0
>
>
> 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
(v7.6.3#76005)