[
https://issues.apache.org/jira/browse/ARTEMIS-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16212641#comment-16212641
]
ASF GitHub Bot commented on ARTEMIS-1472:
-----------------------------------------
Github user tabish121 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1601
Not trying to criticize really, just seems like we should try and make it
easier in a way that leverages the logging and logging config that way you
could control easier the level of granularity on what you are getting and
narrow it down when trying to find specific issues.
While the 5.x stuff is far from perfect it does use a separate logger for
frames which you can toggle on or off in the log4j.properties file to help you
filter AMQP code debugger data from the frame tracing.
> Use PN_TRACE_FRAME as a signal for System.out logging on AMQP events
> --------------------------------------------------------------------
>
> Key: ARTEMIS-1472
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1472
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: AMQP
> Affects Versions: 2.3.0
> Reporter: clebert suconic
> Assignee: clebert suconic
>
> AMQP developers will usually set PN_TRACE_FRM as a System.property to get out
> some information from Proton regarding the frame processing.
> It would be a nice idea to also throw some log.info when that property is set
> at Artemis.. around AMQP Processing, making it easier to Debug AMQP packets.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
