[ https://issues.apache.org/jira/browse/DISPATCH-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chuck Rolke resolved DISPATCH-1082. ----------------------------------- Resolution: Fixed Fix Version/s: 1.4.0 Actually fixed last minute in 1.3. Setting to 1.4 so that this issue is reported and closed in next release cycle. > Log messages can not be correlated to a specific connection > ----------------------------------------------------------- > > Key: DISPATCH-1082 > URL: https://issues.apache.org/jira/browse/DISPATCH-1082 > Project: Qpid Dispatch > Issue Type: Improvement > Affects Versions: 1.2.0 > Reporter: Chuck Rolke > Priority: Major > Fix For: 1.4.0 > > > Several components use 'connection name' which is not unique. > * Policy logs indicating allow/deny at protocol level > * Connection setup > A simple improvement is to include the connection_id integer at the beginning > of the messages. The format should be the same as the prefix added by the > server to proton transport tracer messages. > Log files could be processed simply with > {{ grep '\[4]' router.log}} > to reveal connection setup, authenticated username associations, policy > decisions, and AMQP frame traffic. > This addition would also make it easier to scrape the log file for low-level > connection life cycle details with no ambiguity. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org